Dependencies in the PPA for Jaunty

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Ferlito wrote:
> Currently bzrtools and bzr-svn packages are dependent on the bzr
> package they are released alongside.
...
> I'm thinking of relaxing this to be 
> 
>     Depends: bzr (>= 1.16~)
> 
> for all plugins so that we aren't forced to release a new version of
> every plugin every release cycle.

> Does anyone see any issues with this?

There is still enough fluctuation in the bzr API that I am not
comfortable saying that bzrtools works with any version other that then
one it was released for.  I don't want people getting broken setups and
blaming it on me because the dependencies weren't strict enough.  At the
very least, that requires running the bzrtools tests with that version.

For example, I wasn't expecting the bzrtools 1.15 to need any updates.
But it turned out there was an API break which broke the test suite, and
I had to update for that change.  Had bzrtools 1.14 depended on bzr
(>=1.15~), people could have had incompatible versions of bzrtools and
bzr installed.

I would expect the bzr-svn issues are worse than the bzrtools issues,
because it implements core objects like branches, and we are much more
likely to change the API in ways that are incompatible with implementing
code than in ways that are incompatible with client code.

So my impression is that the strict versioning requirements are entirely
necessary and should not be changed.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko2Rd0ACgkQ0F+nu1YWqI2LTACeL/OCZpO2FOAphlpciRN5FF45
pMEAnAyj01P+2AtkL3BZuwzN4h9yXnDY
=UiVb
-----END PGP SIGNATURE-----