binaries of bzr

Robert Collins robertc at robertcollins.net
Thu Jul 12 05:54:09 BST 2007


At the moment we host several different binaries of various bzr
versions. I'm about to refresh the build process for this, because the
new .so extensions mean that our prior builds won't be sufficient - we
need the architecture specific stuff built too.

So I'd like to make sure I have a clear picture of what folk want/need
so that I can do it all in one hit.

Heres what I'd like:
 - One repo with daily binaries of trunk for
dapper/edgy/feisty/gutsy/unstable/sid for i386/amd64
   - during rc these stop being updated and become rc builds only
 - Another repo with just the latest stable release for the same
platforms
 - A volunteer to do the same for redhat/suse

I'd like to expand what we package as well - make sure a wide selection
of plugins are packaged (e.g. bzr-email, bzr-dbus, bzr-avahi, bzrtools,
bzr-gtk, bzr-eclipse ...)

The bulk of this is just a for loop and clearly not hard :). I have a
amd64 machine at home I plan to build these on for now, it should be
able to build the i386 versions too.

On the packaging front, we need to consider whether we should package
the .so modules separately - that is have
bzr : the bzr application and bzrlib
bzrlib-modules : binary modules to accelerate bzr
or just munge them into one package.

What else would be nice? Any cool ideas?

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070712/252c7b0b/attachment.pgp 


More information about the bazaar mailing list