David Douthitt wrote: > > There's an annoyance that comes up only in development, > and I was wondering how others handle it. > > The problem is this: a development cycle (for me, anyway) > goes like this: boot, fiddle, doesn't work.... fix, > reboot, fiddle, fiddle, reboot, fiddle... NOW it works... > > However..... NOW the disk image is configured for my > environment, and needs to be cleaned out. > > The usual way is to go back through ALL configurations, > reading and using grep, et al. > > Isn't there a better way? > > I was wondering... what if you set up some sort of new > <pkg>.cf (for configuration files) or <pkg>.sane (for sane > configuration :) file (or whatever it is) that allows you to > ERASE those files entirely. This would assume that the > configuration files are matched by <conffile>-dist > files for example...
This is pretty much where Serge Caron came in with `enclosures' . . . at least, part of his enclosure construct does exactly what you describe . . . -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ------------------------------------------------------- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
