bzr-plugin-info [suggest plugins at runtime]

[Robert Collins]

On Wed, 2010-03-03 at 17:01 +1100, Martin Pool wrote:
> Talking to Ian about this a few more points come up:
> 
> Perhaps 'plugin-directory' would be a better name?

I'm fine with that.

> He would like to merge the plugin guide into bzr-plugin-info; I suggest by:
>  * putting the list of all plugins into plugin-info
>  * putting some of the information about the contents of particular
> plugins into the plugins
>  * putting the 'how to write/install a plugin' text into the bzr core docs

Yes please.

> I think for this to achieve its full potential it should normally be
> installed by default,

I agree with this, and that we can do it without it being in core.

>  but perhaps we can make reasonably sure of that
> without it being in the core.  There is at least one strong reason for
> it not to be, which is that we can potentially update this even for
> stable series to tell people about new or changed plugins, and we
> could ship it now for 2.1 (and maybe 2.0?)  We should make sure that
> it gets packaged for all the systems though.
> 
> If we want a good plugin system we have to work it; just folding
> things into core would be kind of avoiding the issue.

Totally agree. I gave a talk at europython with ddaa some years ago
where we described all the positive things having a strong emphasis on
plugins has brought us.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20100303/3466942b/attachment.pgp