Bzr plugins *must* die!

[Jelmer Vernooij]

Hi Erik,

On Wed, 2008-09-24 at 10:21 +1000, Erik de Castro Lopo wrote:
> I run a Hardy base system and have a Dapper chroot. I have a number
> of projects under Bzr and need to be able to compile and test them
> under both Dapper and Hardy. In order to get a compatible Bzr on
> Hardy, I use the one from ppa.launchpad.net.
> 
> This morning I apt-get update/upgraded the Dapper chroot and about
> an hour later found that the new Bzr (1.7-1~bazaar1~dapper1 which
> replaced 1.6.1-1~bazaar1~dapper1) wouldn't load one of the Bzrtools 
> plugins (bzr shelve) because the version of Bzrtools (also installed
> with apt-get) was not the right version.
This sounds more like a specific packaging bug to me rather than a
structural problem.

> So, here we have version problems with plugins making the otherwise
> stable base tool un-reliable. Is it not an obvious solution to pull
> many of the very stable plugin packages into the main bzr tree?
Pulling code into bzr.dev has other consequences as well though; it
becomes harder to contribute to those plugins (review etc for bzr.dev)
and it becomes harder to change their UI because of backwards
compatibility requirements.

For some of the bzrtools commands that have proven themselves, that
makes sense. What other plugins would you suggest to be merged into
core ?

Cheers,

Jelmer
-- 
Jelmer Vernooij <jelmer at samba.org> - http://samba.org/~jelmer/
Jabber: jelmer at jabber.fsfe.org