On Thu, Jan 10, 2013 at 06:38:38PM -0500, Michael K. Johnson 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. > local cooks discover build requirements against the fully-installed system. > > 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.
that's not what i meant. i am asking about cooking something that has dependencies that are not already installed on fdev (but do exist in the fl repo) > > 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. again, i am talking about development builds that are not meant to go into the repo (yet) > > 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... :) well, you said: > > > Please don't use this system for general work. which i take to mean i shouldn't use the rmake server for development builds that are not for the repo... greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix services: debugging, programming, training, linux sysadmin, web development -- pike programmer working in china societyserver.(org|net) foresight developer community.gotpike.org foresightlinux.org unix sysadmin (open-steam|www.caudium).org realss.com Martin Bähr http://societyserver.org/mbaehr/ _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
