[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: common function handling in maintainer scripts



also sprach Stephen Gran <sgran@debian.org> [2005.02.25.0032 +0100]:
> My question is: can I source it in config as well?  I suspect not,
> because of the preconfigure run that apt does.  I suppose if
> I really wanted to do this, I could exit 0 at preconfigure time,
> and only run it at configure, but that seems wrong to me.

Yeah, I think this is the problem, and no, you should not prevent
the preconfigure run. I think you'll have to use redundant code,
although I like the idea of having a *.common control file
installed, which you can use for such a purpose. I suggest you bring
this forth to the dpkg team!

> The second question is (on a completely unrelated note): is there
> any problem with assuming the presence of a color capable $TERM

Yes.

> and is
> anything likely to break if I do?

Output will be unlegible, as it will be interspersed by escape
codes.

> I have seen other linuces that use coloration in init.d scripts
> for success and failure, and I thought it looked kind of cool.
> Since it's easy, I was thinking about doing it in the binary
> packages, but I wanted to ask if it was a bad idea first.

Uh, make sure you read over the policy, please. I don't think it's
allowed to use colour in the init.d scripts. Which other packages do
so? This isn't RedHat, you know? :)

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!

Attachment: signature.asc
Description: Digital signature


Reply to: