On Fri, Jan 11, 2013 at 06:34:54AM -0500, Michael K. Johnson wrote: > And I've been trying to say that in general, fdev isn't intended to > replace a local development system.
of course. it helps though when i am on the road. also over here network access is so slow at times that it can take forever to download all packages for a chroot. (i usually start a local build first, and then try fdev while i wait for the chroot. i do have a proxy, and i just increased the cache time to 90 days to see if that helps things) > Additionally, we can install a few more packages from the repository > to help with that. But we're going to stick with packages from the > fl:2-qa groups and not install locally-cooked packages on fdev. of course, i never expected anything else. > If you need to do an rmake build that might not be ready yet for > repositories but is part of building packages that will end up > in foresight repositories, that's OK... ah, yes, that is what i was after, thanks. > If you would have done a build in rmake on the old fdev, now do it > on rmake.foresightlinux.org. > If you ran screen, irssi, git, mercurial, ... on the old fdev, keep > doing it on the new fdev. i didn't know that doing things like running irssi would have been acceptable. i was using rmake occasionally for non-fl builds because it appeared to not be in use, most likely due to timezone differences. > Does that make more sense? it does, thank you! 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
