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... thoughts? I don't really have any input on it, aside from I'd > > like to gather what people want/think would be useful. > > Another good idea, would be "pending jobs" list. Many ebuilds provide > imports instructions like "you can now delete this or that config-file" > or like "you must immediatly run this or that". > > These usually scroll by while there're nobody watching the screen and/or > they cannot be read completely, since they scroll away too fast. logging (and post display) of info/warning, it's in head. > 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 know about them. So /etc/ will be full of > useless config-files after some time. 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.
This would cause issues for nvidia-kernel though I'd think, although their solution isn't exactly optimal (no better solution atm either though). ~harring
pgpGI7KDmu7aL.pgp
Description: PGP signature
