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 whether the previous and new ebuilds
have compatible configuration file formats (similar to EAPI) and only
restart the service if they are compatible.
Interesting. Something like PKG_CONFIG_VER, individualized for each
package. Portage would know not to restart the service between major
versions, and would know it could if the version stayed the same. The
question would be what to do for minor config version changes (which would
equate to compatible in general, but with one or more changes). I'd say
that should mean a safe restart as well. If it wouldn't be safe, and
since the config version would be a Gentoo-only arbitrary number, I'd say
make that a major version change.
I mentioned this mostly just because the idea popped into my head and thought others
might be interested ;-). Upon further inspection, it does seem like a "opening can
of worms". I'm not sure that the benefits of this feature would justify the costs
of implementing it.
Zac
--
[email protected] mailing list
