[cap-talk] Multi-distribution builds (was Re: Session failures)
Steve Beattie
steve at nxnw.org
Mon Mar 31 12:17:12 EDT 2008
On Fri, Mar 28, 2008 at 09:13:20AM -0400, Jonathan S. Shapiro wrote:
> On Fri, 2008-03-28 at 02:34 +0000, Toby Murray wrote:
> > Or if self-hosting the devel environment isn't possible yet, build a
> > second VM image that is a standard linux install that includes your
> > cross tools, already built and ready to go. This saves having to
> > maintain cross tools for multiple distributions. You just say: "we
> > support Fedora Core X, or whatever."
>
> Toby:
>
> We currently support several editions of Fedora, and I have considered
> at various times building packages for Ubuntu. The main impediment in
> practice is setup time, but once we get the setup working there is
> really no difficulty. Putting out a pre-installed VM doesn't really
> help, because it doesn't solve the problem of keeping the tool chain
> upgraded.
>
> I haven't tried it, but I have the impression that the Fedora packages
> should work on CentOS without any problem -- at most they will need to
> be rebuilt.
>
> I'ld be willing to package for Debian and Ubuntu, but I need some help
> to do that -- mostly in the form of advice:
>
> - I haven't run these systems, so I don't really know how their
> release numbering/naming schemes work. What releases should we add
> to our package build farm?
>
> - In the Debian world, there seem to be many forks. I'm not clear
> whether we need to build separate packages for all of them or we
> can re-use some of our packages for multiple releases.
>
> - I don't know where to find documentation on building debian-style
> packages. What I need is the equivalent of Maximum RPM. Can somebody
> tell me where to find that?
>
> Finally, I don't know what other releases we should perhaps consider.
>
>
> The timing of this is actually pretty good right now. We're entering a
> lull, and I was going to use some of that time to rearrange our
> infrastructure.
You might want to look at the openSUSE build service
<http://en.opensuse.org/Build_Service>; in addition to supporting
automated builds on various openSUSE distributions, various Fedora,
Centos, Debian, Ubuntu, and Mandriva versions are supported. The resulting
builds are then made available in apt/yum/yast compatible repositories
for your community to use as installation sources.
There was some token support for having the build service repository use
a remote svn tree as a source; I don't know if it's now possible to have
it automatically pull from a mercurial tree.
(I'm not affiliated with openSUSE, just a happy user.)
--
Steve Beattie
<steve at nxnw.org>
http://NxNW.org/~steve/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://www.eros-os.org/pipermail/cap-talk/attachments/20080331/2b69448b/attachment.bin
More information about the cap-talk
mailing list