bzrtools etc into the ppa (was Re: bzr 1.8 release plans)

[Martin Pool]

On Tue, Oct 14, 2008 at 2:17 AM, John Arbash Meinel
<john at arbash-meinel.com> wrote:
> > There is a copy of bzr in the PPA, but currently no bzrtools, even
> > though there is a 1.8.0 upstream release.  As far as I can see
> > bzrtools has not yet been updated to use the builddeb system used for
> > bzr.

1.8 final is now in the PPA, as is bzrtools 1.8.0.

> There is a branch that Jelmer has for packaging bzrtools for debian,
> which works just fine for packaging bzrtools for gutsy/hardy/intrepid (I
> don't think it is correct for dapper.) Which is what I've been using.
>
> There are branches for:
> lp:~bzr/bzrtools/packaging-dapper
>
> etc,
>
> Though I've been doing it as an all-in-one package:
> lp:~bzr/bzrtools/ppa
>
> Basically, I use the same basic process, but I do it all in the same
> branch. I merge Jelmer's build branch into this, fixing changelog. Then
> I update the changelog for gutsy, commit, build. Update for hardy,
> commit, build, etc.

Right, that's what I was previously doing for bzr.  Although in some
ways it's simpler, it does have the drawback that it doesn't work with
dapper, which needs different debian/control information, and now that
more of the update process is getting automated I'd like to make it
consistent across bzr, bzrtools, and other things we may package.

So if it's ok with you, I'd like to keep
lp:~bzr/bzrtools/packaging-dapper etc as the definitive sources,
though of course we can merge between them.  In fact I've done this.

Now we should be able to use very similar scripts to upload bzrtools.
(For reasons that aren't totally clear to me, bzr builddeb needs
--merge to build the bzrtools deb but not for bzr, even though both
just have the contents of debian/ in the packaging branch.)

--
Martin <http://launchpad.net/~mbp/>