should declare minimum bzr version

[Marius Kruger]

bzr explore with bzr version 1.13.1 explodes because we use hidden Options
which was snuck in just after 1.13.1 .

So I think it would be useful to check a minimum bzr version which should at
least be 1.14 at the moment. Rather just tell the user his bzr is too old.

[Alexander Belchenko (bialix)]

It should be easy to fix. Wanna provide a patch? ;-)

[Marius Kruger (amanica)]

2009/7/9 Alexander Belchenko <email address hidden>

> It should be easy to fix. Wanna provide a patch? ;-)

sure, I'm planning to, but I don't know when I'll get round to it.
so I don't want to make promises.
I thought I'll log it now and mark it in progress if/when I start.

[Alexander Belchenko (bialix)]

merged as revno 182.

[Alexander Belchenko (bialix)]

We don't need to release new version of bzr-explorer every time as bzr.dev will change its API version. So I simply use hidden options when they are available. Because these options are intended for developers there is no harm IMO.

[Marius Kruger (amanica)]

2009/7/21 Alexander Belchenko <email address hidden>:
> We don't need to release new version of bzr-explorer every time as
> bzr.dev will change its API version. So I simply use hidden options when
> they are available. Because these options are intended for developers
> there is no harm IMO.

thats even better, so that we can at least support 1.13 (which is in jaunty),
but I think we need to draw the line and say what the minimum
supported version is.
After your new change it can be 1.0.0 or 0.0.1 ??? I don't know what the oldest
supported bzrlib version is,
but I guess we can forgo to check until somebody makes it crash again because
of a old bzrlib, and add it again at that stage.
I think we need to set some minimum.

[Alexander Belchenko (bialix)]

Marius Kruger пишет:
> I think we need to set some minimum.

It will be nice to have proper support in bzrlib first to check only
minimum version.