bzr --version should also report plugin versions (bzrlib ...)

[Marius Kruger]

On 8/6/07, John Arbash Meinel <john at arbash-meinel.com> wrote:

> I didn't strictly suggest it. But it actually might be a reasonable idea
> so it is easier to eyeball. (Oh, this is bzrlib 0.18, and bzrtools 0.17).
>
> However, many plugins have a very different set of version numbers
> (bzr-svn is at 0.4.x, bzr-gtk may or may not follow bzrlib version
> numbers) Obviously some plugins do. bzr-svn has very strong reasons not
> to, because it is declaring compatibility with itself, which is actually
> quite important. I suppose Jelmer could do "0.3.XX.1" releases, where
> "XX" indicates compatibility with that version of bzrlib. But since we
> release a new bzrlib every month, that could get to be a real
> maintenance nightmare.
>

Another option would be for the plugins to publish what their minimum
required bzrlib version is,
that way they can keep their own version numbers and still make it
known what they require (or recomend?)

eg. bzr-svn version 0.4.x (requires bzrlib 0.17)

another advantage is that we can move the bzrlib version compatibility
checking code into bzr and out of the plugins,
and thus handle compatibility issues more uniformly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20070806/1bb99aaa/attachment.htm