On Wed, Sep 27, 2006 at 11:49:46PM +0400, Sergei Golovan wrote: > On 9/27/06, Bill Allombert <[EMAIL PROTECTED]> wrote: > >The ejabberd postrm include the following:
> > purge) > > ucf --purge $CONFIG_TARGET > > rm -f $CONFIG_TARGET > > rm -Rf /etc/ejabberd /var/log/ejabberd /var/lib/ejabberd > > rm -f /etc/default/ejabberd > > deluser ejabberd 2>/dev/null || true > > delgroup ejabberd 2>/dev/null || true > > ;; > >The postrm script cannot rely on ucf and adduser to be available when > >purging. > Well, it's easy not to use adduser (and use userdel and groupdel from > passwd). > But if config is managed by ucf then how can we purge it without ucf? > Does it mean that ucf is unusable for config management? That's a good point. We seem to have two conflicting policy requirements here: the requirement for a package's purge to reset it to a completely pristine state, and the requirement to not rely on non-essential packages on purge. I'll check with Manoj on the question of how to best disambiguate this, if it's indeed possible. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
