| 1 |
Mike Frysinger wrote: |
| 2 |
> On Wednesday 20 July 2005 05:54 pm, Brian D. Harring wrote: |
| 3 |
> |
| 4 |
>>Out of curiousity, has any put any thought into some automated method |
| 5 |
>>or hook for allowing restarting of rc-scripts on upgrade/re-emerge of |
| 6 |
>>a package? |
| 7 |
> |
| 8 |
> |
| 9 |
> such a completely automated thing is a bad idea ... detecting and warning |
| 10 |
> though isnt a bad idea ... too many issues such as config files may need to |
| 11 |
> be upgraded or maybe a config file was edited but admin doesnt want to |
| 12 |
> restart the service just yet, etc... |
| 13 |
> |
| 14 |
|
| 15 |
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. |
| 16 |
|
| 17 |
> this probably falls under the pkg_{pre,post}inst gathering code bug ... but at |
| 18 |
> the very end of an emerge process, i think that there should be a summary of |
| 19 |
> packages which were upgraded and have a running init script ... detecting |
| 20 |
> whether a given init script is running is trivial, just ask us base folk on |
| 21 |
> irc and we can point you in the right direction |
| 22 |
> -mike |
| 23 |
|
| 24 |
This feature could live happily alongside the other one. |
| 25 |
|
| 26 |
Zac |
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives