Hi Erich, > Either way, what is the canonical way to keep an existing build > environment in sync with CVS. Buildtool does not check for modifications > once a package is built. since nobody else chimed in (and since I'm partly to blame for some of the shortcomings of buildtool), I'll respond - I'm not aware of any means of doing that, without starting from scratch.
The way I always went when I wanted to make sure I was up to date was to change the cvs-sourceforge definition in sources.conf to point to my local (up to date) cvs checkout (the skeleton for that change is already in conf/sources, commented out), remove conf/installed and everything in source/, build/ and staging/ and then run ./buildtool.pl build buildenv [+whatever else packages one wants] I'm not aware of a more efficient way to do that. Martin ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
