This is an update to my previous post with more information. At this point, this information should be stable, and if someone would volunteer to make a wiki page from this email, I would appreciate your effort.
For those of you with fdev accounts, fdev is now fully operational. fdev is now a foresight-based system. This means, among other things, that the packaged conary/rmake contexts are available. Replace any custom contexts for foresight builds by: Add to your ~/.conaryrc on fdev: includeConfigFile /etc/foresight/development/conary.conf Add to your ~/.rmakerc on fdev: includeConfigFile /etc/foresight/development/rmake.conf fdev is now part of a multi-node rMake cluster, not just a single build machine with a single local rmake. This means that it's not just a replacement for your personal system for building. It also means that you need to authenticate to talk to rmake. It uses rBuilder Online as its authentication engine. You'll need to add to your global rmake configuration a line like: rmakeUser rBuilderOnlineUserName rBuilderOnlinePassword Be aware that after you commit, it will take some relatively short amount of time for your commit to be visible in the public foresight repository. Currently, a mirror is started every minute on the minute if there isn't currently one running. This means that as long as there is nothing currently being mirrored, your commits to foresight-commits will usually show up within a minute. (If a kernel commit is currently mirroring, it might take a little longer.) For your development systems, please make sure that your system conary configuration uses the main repository. Your user conary configuration should use foresight-commits. Please do not use foresight-commits for system updates! Doing so will destroy the point of separating the commits-heavy repository from the one that specializes in updates, and will get in the way of other developers. Remember that /home is not backed up on fdev. Continue to plan accordingly. Finally, please be on #foresight-devel while using fdev, as I will be announcing there when I do maintenance. I'll be updating systems from time to time. _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
