Julian Andres Klode wrote: > On Wed, Mar 31, 2010 at 12:07:11PM -0700, Greg KH wrote: >> On Wed, Mar 31, 2010 at 08:48:52PM +0200, Julian Andres Klode wrote: >>> On Wed, Mar 31, 2010 at 07:41:26PM +0100, Peter Robinson wrote: >>>>> It's there when you select a branch in the web ui, see e.g. >>>>> http://gitorious.org/meego/meego-rpm-config/commits/master >>>>> >>>>> For some reason many projects do not have any branches visible in the >>>>> web UI... maybe that's just a matter of time until some crawler at >>>>> gitorious does its magic? >>>> Yes, its there for head but I can't find the same for each tagged release. >>>> See >>>> http://git.moblin.org/cgit.cgi/mx/ for an example. Each tag has a >>>> corresponding download link to .zip .tar.gz and .tar.bz2 >>> Just replace the 'master' with the name of the tag, e.g. >>> http://gitorious.org/meego/meego-rpm-config/commits/0.4 >>> brings you to >>> http://gitorious.org/meego/meego-rpm-config/archive-tarball/0.4 >>> >>> But normal tarballs are better anyway for distributions wanting >>> to package parts of MeeGo for their own use. >> That's what the build service is for, hopefully that will all be made >> public soon... > > I fail to see how the build service is related to packaging on > distribution level. The build service builds binary packages, > whereas we would need the source tarballs to package software > for Debian which can then be built by Debian's buildd network.
The build service takes source and produces repos - binary and source. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
