[Pkg-bazaar-maint] [RFC] Plugin property API

[Jelmer Vernooij]

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

Robert proposed some interfaces for defining the properties of Bazaar
plugins a while ago, as documented in doc/developers/plugin-api.txt.

I'm considering using this sort of information to automate the
updating of the dependencies in the Debian Bazaar packages, and as
such I plan to submit patches to add this information to the plugins
that are part of the Debian archive at the moment.

With the current infrastructure the minimum and maximum version of bzr
that is supported will have to be specified in two places: __init__.py
(a range of API versions that's supported) and setup.py (a mimimum and
maximum bzrlib version). Since this information is updated regularly
(pretty much every bzr version) I'd like to specify it only once, in
setup.py.

I'd like to either add a function that checks for the compatibility of
a bzr plugin based on a setup module, e.g.:

from bzrlib.plugins.svn import setup
check_plugin_api(setup)

This could then take care of checking the minimum/maximum supported
versions as declared by the plugin. Unfortunately it would mean an
extra import per plugin (for the setup file). Would anybody object to
such a function?

Also, would it perhaps make sense to merge the plugin-info into bzr
core, maybe as hidden command for now ?

Cheers,

Jelmer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iJwEAQECAAYFAkpgVtEACgkQDLQl4QYPZuW4VwP/XoqWA6njSYUu3Bllyjr+bnkg
UL8FSUZNuRml2dS6NPYORDYlXGkbFlE9IcMNUyDMB9fywWvKb+IzklzRnKk4a17n
MmzeS3LcVAb+yRIfRYJ/ko5H++7ZwEm1ERgyAvJrI3v71UCnScgByDHDC7Fx6D4H
/nU/OqghSITtWIeGe3c=
=oiEx
-----END PGP SIGNATURE-----