On Wed, Jan 25, 2012 at 04:14:10PM -0200, Christian Robottom Reis wrote: > On Tue, Jan 24, 2012 at 10:50:51AM -0500, Chris Lalancette wrote: > > In terms of finding things in the future, I have to say that there > > is a bit of a forest of git trees in linaro. At the very least, I > > would make sure that the .dsc file in the released deb points to the > > correct tree+tag that it was generated from. > > That's not a bad idea. John, can we make that happen? > > > 1) Attempt to reduce the number of trees on git.linaro.org. I > > understand that there is probably a lot going on, but the sheer > > number of trees makes it confusing. It might be a good idea to > > remove some of the very stale or no longer active trees. > > What do Deepak and Lo?c think of this in general? > > > 2) Document on the wiki where the releases are built from, so there > > is a running record per release > > Where would we record this, Deepak, Alexander, Lo?c?
For Ubuntu, I think the (only) correct way to track this is to represent linaro releases as actual releases in the package archive. i.e., sources.list will look like deb http://ports.ubuntu.com/ubuntu-ports precise main deb http://ppa.launchpad.net/linaro-maintainers/overlay linaro-12.02 main And http://ppa.launchpad.net/linaro-maintainers/overlay/ubuntu/dists/linaro-12.02/Release and the things it points to would then be authoritative definition of what was in that release for evermore (or at least, the GPL-requisite 3 years). Once we have this, we can document robustly how to find out, because the means to do so will be stable and not constantly changing. Do you know if this is sensible/doable, or is launchpad very tied the ubuntu release names? Cheers ---Dave _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
