On Tue, Aug 25, 2009 at 10:28:42PM -0400, devnet wrote: > The Foresight repository should be restructured to use the appliance > model that other products already use so that when the new UI is in > place, you can actually browse images and releases...as it is now, you > can't. So, as it is now, when the new UI goes into effect, developers > won't be able to find image builds (developer snapshots) on Foresight. > It's going to really get messy soon.
This doesn't require "restructured" at all. > I know that boots will be built using the appliance based model of > organization for the repository (most likely, using the rbuild tool). Not using rbuild, no. Let's not get hung up on "appliance". It will be an import built with mirrorball (http://hg.rpath.com/mirrorball or http://bitbucket.com/rpathsync/mirrorball) which is designed for massive import tasks like this; rbuild is built for a different kind of task. Again, please look at Scientific Linux 5 delivered by rPath for an example of what this will be like. > Trying to match that to Foresight, which isn't organized in this > fashion, will be like matching oil to water. I'm not sure I understand this. There will be packages on labels in Conary repositories. What's the oil and water? > I think, before we talk about starting a new repository with boots > goodness, we should fix the repository (using rbuild tool) we have so > that it, in the future, will be compatible with the UI _and_ other > products like boots. Until then, we're traipsing down the rabbit hole > and it will be harder to get back the further down we go. rbuild is the right tool for automating many repetitive tasks when building a product on top of an existing platform. rbuild is the wrong tool for building boots. It's also the wrong tool for building foresight linux -- it does a lot of "figure out the right thing to do" that makes it so great for product development but becomes intractably slow when you are trying to deal with thousands of packages, because it tries to do work that isn't useful, necessary, or relevant to the from-scratch platform building case. It wasn't designed for that. "compatible with the UI" doesn't require "fix the repository" and there's no rabbit hole to traipse down; nothing's getting harder here. _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
