Improving the distro packaging and installation experience

[James Westby]

On (07/12/06 23:15), Etienne Goyer wrote:
> However, I believe sarge use python 2.3, and that bzr require 2.4, so I
> am not quite sure we could supply a package that work on sarge.  Please
> someone correct me if I am wrong here.

Spot on.

As etch isn't far away Sarge isn't too much of a concern I think.

> > Here's the challenge: come up with a way to build packages every day for
> > all of those environments, so we shake out issues during the development
> > cycle rather than at release time.
> 
> As far as .deb for Ubuntu/Debian are concerned, I think it would be
> possible to entirely automate the process.  Here is what I propose :
> 
> - Auto-build daily package targeting edgy/feisty/etch/sid, and upload
> them to http://bazaar-vcs.org/packages/debs.
> 
> - Build release packages (including RC) targeting dapper, and upload
> them to http://bazaar-vcs.org/releases/debs.
> 
> If that suit everybody, I could start doing that in short order.

I can volunteer to run a daily cron job for sid/etch. I can't promise to
do more than that (as in fixing breakages), but I have the chroots if
you want to make use of them.

> 
> Also, should bzrtools be systematically packaged alongside bzr ?  Are
> there any other "must-have" plugins that we should consider adding to
> this effort ?
> 

I think packages of bzrtools and bzr-gtk would be good, but I'm not sure
that daily builds are necessary there. When I have some time I am going
to finish of the packages of webserve, so that they will be available
for .deb distros, and I could build them regularly for separate
distribution if that was wanted.

Would this be a good time to start looking at some trial implementations
of direct builds from bzr branches on request?

Thanks,

James

-- 
  James Westby   --    GPG Key ID: B577FE13    --     http://jameswestby.net/
  seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256