I have finished the process of splitting the foresight repository into two repositories.
All commits will be made to the new foresight-commits repository. Those commits will then be immediately mirrored out to the main foresight repository. This makes foresight development and system updates mostly independent from a performance perspective. Foresight end users will never need to know the difference. Things should just work better, without a perceptible change. Foresight developers will need to adjust, very slightly. * Please DO NOT use foresight-commits for system updates. Your system conary configuration should not include a repositoryMap entry for conary-commits. * You SHOULD, however, have a repositoryMap entry in your own user conary configuration. Add a line to your ~/.conaryrc file for your normal user (not root!) that looks like: repositoryMap foresight.rpath.org https://foresight-commits.foresightlinux.orc/conary/ _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
