On Friday 11 November 2005 20.30, Richard Fish wrote: > On 11/11/05, Jimmy Rosen <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Well, it's not that I don't want them modified by new baselayout. > > It's just that I would like to have the convenience of using > > etc-update to remind me that I need to update them manually. > > I have some modifications in those files that allow me to boot a > > diskless cluster from a single regular gentoo installation. > > Right now I always watch very carefully when I have to bring in a > > new baselayout since I have to keep those two scripts working. > > But I have been known to forget. > > I also have modifications in a few of the critical /etc/init.d > > scripts as well, but they are caught by the CONFIG_PROTECT and > > I'm immediately reminded to update and manually merge my > > functionality changes when a new version is in. > > > > So this is essentially just for me to get autoreminders when they > > need attention. My teflon memory is dangerous enough, and I need > > all the help I can get from automated tools and reminders. > > Well, this is probably evil, but I like it anyway: > > Edit /etc/portage/bashrc and add: > > test /sbin/rc -nt /sbin/rc.safe && printf "\n**** /sbin/rc needs to > be updated NOW **** \n\n" > > Then when you update baselayout and a new /sbin/rc comes along, you > will get a notice after it is merged but before the 'clean'step > runs. Presumably you can then diff /sbin/rc and /sbin/rc.safe to > figure out the differences.
Muahaha, super. Evil indeed. But it seems like a good enough supplemental workaround, so I'll try it out. Thanks for the help Jimmy -- gentoo-user@gentoo.org mailing list