make upgrade overwrites /etc/mail/mailer.conf

Jonas Trollvik jontro at gmail.com
Tue Feb 8 02:05:37 PST 2005


If an upgrade adds a service you dont want there is something wrong
with the upgrade. Isnt the thought that all the services that'll be
added are required for the system to function properly exactly just
like a user is added automatically?
Why else would be the point of this?


On Mon, 07 Feb 2005 21:28:20 -0500, David Cuthbert <dacut at xxxxxxxxx> wrote:
> Matthew Dillon wrote:
> >     I don't think it's necessary that we support service removal
> >     immediately, but if we were to do it I would suggest something like
> >     '-<servicename> ...' in /etc/services to remove a service entirely.
> 
> Oof.  This misses the (common) case where an upgrade adds a service I
> don't want.  I didn't remove it because I was unaware of it before.
> 
> I'm somewhat fond of the way portage handles this (or, at least, is
> supposed to): modify an example configuration file which is used for
> reference only.  /etc/make.conf, for example, is never touched;
> upgrading portage modifies /etc/make.conf.example.
> 
> Dave
>





More information about the Bugs mailing list