Mike Frysinger wrote:
On Wednesday 20 July 2005 05:54 pm, Brian D. Harring 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?
such a completely automated thing is a bad idea ... detecting and warning
though isnt a bad idea ... too many issues such as config files may need to
be upgraded or maybe a config file was edited but admin doesnt want to
restart the service just yet, etc...
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 whether the previous and new ebuilds have compatible configuration
file formats (similar to EAPI) and only restart the service if they are compatible.
this probably falls under the pkg_{pre,post}inst gathering code bug ... but at
the very end of an emerge process, i think that there should be a summary of
packages which were upgraded and have a running init script ... detecting
whether a given init script is running is trivial, just ask us base folk on
irc and we can point you in the right direction
-mike
This feature could live happily alongside the other one.
Zac
--
gentoo-dev@gentoo.org mailing list
