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...
Perhaps:
cd /var/lib/lrpkg
for i in $(cat $PKG.cf) ; do
mv ${i}-dist $i
done
rm $PKG.cf
apkg -s $PKG # save package...
The other annoyance in development is this - to restate
the above dev. cycle slightly:
booooooooooooooooooooooooooooooooooooooooot.....
diddle, diddle, fix, reboooooooooooooooooooooooooooooooooooooot....
diddle, patch, fix, save, rebooooooooooooooooooooooooooooooooooooot....
You get the idea :-) What's the best way to get around this?
Besides getting a cup of coffee, I mean :-)
I've tried UMLinux but that never did work and seemed to require
a patched system. I think VMWare worked, I forget ....but $300+?
Someday...
-------------------------------------------------------
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
