| 1 |
Duncan wrote: |
| 2 |
> Zac Medico posted <42DF90B1.9030806@×××××.com>, excerpted below, on Thu, |
| 3 |
> 21 Jul 2005 05:10:25 -0700: |
| 4 |
> |
| 5 |
> |
| 6 |
>>This could be an optional feature such as FEATURES="restartservices". The |
| 7 |
>>CONFIG_PROTECT functionality could remain as is. Portage could use a |
| 8 |
>>special ebuild variable to determine whether the previous and new ebuilds |
| 9 |
>>have compatible configuration file formats (similar to EAPI) and only |
| 10 |
>>restart the service if they are compatible. |
| 11 |
> |
| 12 |
> |
| 13 |
> Interesting. Something like PKG_CONFIG_VER, individualized for each |
| 14 |
> package. Portage would know not to restart the service between major |
| 15 |
> versions, and would know it could if the version stayed the same. The |
| 16 |
> question would be what to do for minor config version changes (which would |
| 17 |
> equate to compatible in general, but with one or more changes). I'd say |
| 18 |
> that should mean a safe restart as well. If it wouldn't be safe, and |
| 19 |
> since the config version would be a Gentoo-only arbitrary number, I'd say |
| 20 |
> make that a major version change. |
| 21 |
> |
| 22 |
|
| 23 |
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. |
| 24 |
|
| 25 |
Zac |
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives