On Sunday 24 July 2005 15:25, Martin Schlemmer wrote:
> On Fri, 2005-07-22 at 18:40 -0500, Brian D. Harring wrote:
> > On Sat, Jul 23, 2005 at 01:20:19AM +0200, Sven Köhler wrote:
> > > Apropos config-files: what about config-files that are provided by
> > > the old-version of an ebuild but have be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian D. Harring wrote:
> Vapier had suggested yanking (on unmerge, not replacement) any
> config_protected file that has the same md5/mtime as what it was
> originally merged with.
As and end-user, that would be mana from heaven. :)
Nathan
-B
On Fri, 2005-07-22 at 18:40 -0500, Brian D. Harring wrote:
> On Sat, Jul 23, 2005 at 01:20:19AM +0200, Sven Köhler wrote:
> > Apropos config-files: what about config-files that are provided by the
> > old-version of an ebuild but have been moved or removed by the new
> > version? etc-update doesn't
On Sat, Jul 23, 2005 at 01:20:19AM +0200, Sven Köhler wrote:
> > Out of curiousity, has any put any thought into some automated method
> > or hook for allowing restarting of rc-scripts on upgrade/re-emerge of
> > a package?
> >
> > Other question is if any such hook is even needed.
> > So... tho
Duncan wrote:
Zac Medico posted <[EMAIL PROTECTED]>, excerpted below, on Thu,
21 Jul 2005 05:10:25 -0700:
This could be an optional feature such as FEATURES="restartservices". The
CONFIG_PROTECT functionality could remain as is. Portage could use a
special ebuild variable to determine wheth
