Bazaar spontaneously unusable

[Aaron Bentley]

On 04/08/2010 09:31 PM, Andrew Bennetts wrote:
> One issue is that I believe the packaging can easily be out of sync with
> the plugin's internal API checks.  So if the Depends field of the deb
> packages reliably stated exactly what the plugin checked at runtime,
> that would be nice (and similiarly for other package/bundle formats).

We could perhaps reuse the install_requires setup.py information?

This unfortunately speaks in terms of packages, not APIs, but with the 
current granularity of versioning, there's no substantial loss.

> It would also make it easier for someone to write a tool that finds all
> the projects in the “bazaar” project group on Launchpad (or just uses a
> hard-coded list of plugins), grabs their latest tarball release (and
> maybe also trunk?), looks at the machine-readable “I require bzrlib
> x.y.z” declarations, and spits out a report saying which plugins need
> updating (or have been updated but need to make a release with the
> update).  Then as a bzr releases draw near someone (the RM, a plugin
> liason, the community in general?) can run the report and remind the
> relevant plugin maintainers to update their plugins.

That would be a great thing.  As a plugin maintainer, I wouldn't mind if 
it emailed me directly, and some of my plugins have enough metadata to 
support that :-)

Aaron