On Mon, Oct 26, 2009 at 08:46:27PM -0400, Michael K. Johnson wrote: > I guess I should report progress: if you are following Conary > commits via http://lists.rpath.com/mailman/listinfo/conary-commits > or http://hg.rpath.com/conary or http://hg.rpath.com/conary/rss-log > or http://bitbucket.org/rpathsync/conary/ you have seen a lot of > commit traffic. It is practically all related to this. Some of ... > I know that a lack of a progress report can give the impression > of a lack of progress, so I wanted to report at least some of > the progress that has been made here.
Just a quick update, again. A significant amount of churn in Conary tip development recently has gone into sane handling on the build side for files shared between multiple RPMs built from the same .src.rpm file and then packaged into capsules from the same :source component. You can see some of what we've been doing by looking at the parent issue: https://issues.rpath.com/browse/CNY-3217 Looking at the changes just to Conary since the last release, 2.0.50, diffstat shows as a summary: 120 files changed, 5770 insertions(+), 1805 deletions(-) That's 3965 net new lines just in the Conary source code associated with this work. Again, I apologize that this work isn't highly visible. We've been doing test imports of large sets of RPMs almost daily. In other news, some of the necessary work will more directly apply to FL3. In particular, python dependency bootstrapping has been fixed to work correctly when bootstrapping one python version with another python version; previously, we could bootstrap one build with another but in the initial bootstrap, python dependencies would not be discovered because it was trying to use the compiled .pyc file with the wrong interpreter. This will allow FL3 to move to Python 2.7 if that's appropriate in the FL3 timeframe, for example. _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
