On Thu, Jan 10, 2013 at 02:00:42PM +0100, Martin Bähr wrote: > hmm, i generally prefer working with rmake rather than cvc cook mainly > to avoid installing to many local dev packages. this wouldn't be an > issue on fdev i suppose, but only if every developer has the ability to > install new local packages. is there a simple solution for that?
Never cook into the repository with a local cook. rmake does clean builds. local cooks discover build requirements against the fully-installed system. Each has its own role. Don't use fdev to test packages you have built. fdev isn't meant to be a replacement for having a development system for significant development. > what if my package depends on another package that i am building myself? > does cvc cook handle that? No, and it's not intended to. For builds into the repository, use only rmake. > barring any solution to that, could a local rmake be running on fdev? if > unused it wouldn't take much resources, but it would be available for > those cases where cvc cook doesn't work. Just use rmake on the rmake server... :) _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
