Automatic Plugin Managment (aka Command not Found)

James Westby jw+debian at jameswestby.net
Tue May 27 14:40:07 BST 2008


On Sun, 2008-05-25 at 03:55 -0300, Martin Albisetti wrote:
> > On Sun, May 25, 2008 at 3:17 AM, Martin Albisetti <argentina at gmail.com> wrote:
> >
> > Of course, it helps if I actually send a patch...
> 
> Gmail is playing tricks on me today, sorry for all the noise.

Hi Martin,

Thanks for working on this. The patch looks pretty simple.

>  class NoPluginAvailable(BzrError):
> -    pass    
> +
> +    def __init__(self, plugin_name):
> +        self.plugin_name = plugin_name
> +
> +    _fmt = '"%(plugin_name)s" is not a recognized plugin.'
> +
> +
> +class PluginAlreadyInstalled(BzrError):
> +
> +    def __init__(self, plugin_name):
> +        self.plugin_name = plugin_name
> + 
> +    _fmt = '"%(plugin_name)s" is already installed.'

Do we want to have "installed and already the newest version?" I'm 
thinking about the case when a plugin adds a new command.

Are these errors to be raised by the "install-plugin" command?

Thanks,

James




More information about the bazaar mailing list