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

[Jari Aalto]

* Mon 2007-08-06 Martin Pool <mbp AT sourcefrog.net>
* Message-Id: e01316480708051435k54ff850bm38d83f13dbde1570 AT mail.gmail.com
> On 8/4/07, Jari Aalto <jari.aalto AT cante.net> wrote:
>
>>
>> I would have a small wish to next bzr version:
>>
>>     $ bzr --version
>>
>>     Bazaar (bzr) 0.18.0
>>       from bzr checkout /usr/lib/python2.5/site-packages/bzrlib
>>         revision: 2
>>         revid: jari.aalto AT cante.net-20070401090549-bigooycypl8hej66
>>         branch nick: bzrlib
>>     Using Python interpreter: /usr/bin/python
>>     Using Python standard library: /usr/lib/python2.5
>>     Using bzrlib: /usr/lib/python2.5/site-packages/bzrlib
>>     Using Bazaar configuration: /cygdrive/x/home/jaalto/.bazaar
>>     Using Bazaar log file: /cygdrive/x/home/jaalto/.bzr.log
>>
>> It would be nice if the plugin version numbers were also reported:
>>
>>     Using bzrlib: /usr/lib/python2.5/site-packages/bzrlib 0.18.0
>>
>> It's a little difficult to grep under
>>
>>     /usr/lib/python2.5/site-packages/bzrlib
>>
>> and decode where the version infomation might be.
>
> Do you mean the plugin versions, or the bzrlib version?  
> I agree it would be good for 'bzr plugins' to show the first, if it
> can find one. 

Plugin versions in general. John suggested that all the info,
including bzrlib, would be moved to "bzr plugins". Somehow the version
number of all plugins should be required. That would help e.g. out of
date detections.

> For the second, the version must be the same as bzr, otherwise you
> get a warning when bzr starts. In fact the number shown at the top
> is the bzrlib version, since the bzr script changes so rarely.

Correct.