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

Re: Release update

Hash: SHA1

> Quoted from Henning Makholm:
> > > What is the reason for this behaviour?
> >
> > It is easy to implement in update-rc.d without needing specific
> > support from the maintainer scripts to tell it whether the
> > package is being installed anew or just updated (or resurrected from
> > removed-but-not-purged state).
> As I understand this (correct me if I'm wrong), when update-rc.d
> is called (.postinst ?) by a package, it is unable to know if it's
> performing an install (create the links) or an update (don't touch
> anything).
> So, update-rc.d is based on a hack, which check if there is at least
> a single link remaining in /etc/rc?.d/ to guess if the package is
> already installed or not.

I'm probably missing  something, but is their any reason way it doesn't just 
check whether the /etc/init.d/<package> script is there? You could then 
then do with the /etc/rc?.d/ links what you want.
- -- 
Cheers, cobaco (aka Bart Cornelis)
1. Encrypted mail preferred (GPG KeyID: 0x86624ABB)
2. Plain-text mail recommended since I move html and double
    format mails to a low priority folder (they're mainly spam)
Version: GnuPG v1.2.4 (GNU/Linux)


Reply to: