I'm working on bzr-config utility (configuration utility for Bazaar with graphical interface) and I'm plan to provide such plugins management:
1) Existing plugins: user can disable plugin or delete plugin completely. When choose disable then plugin moved to ~/plugins/.disabled subdirectory and stay in touch
2) Install new plugins: from the archive (zip/tar.gz) on local disk or from URL. If this is a branch user could do lightweight checkout of plugin (this simplify update process)
3) Using Plugins Registry from http://bazaar-vcs.org/BzrPlugins. Read raw source of this page and parse it. And then user could browse existing plugins and then install them (see above).
I'm working on bzr-config utility (configuration utility for Bazaar with graphical interface) and I'm plan to provide such plugins management:
1) Existing plugins: user can disable plugin or delete plugin completely. When choose disable then plugin moved to ~/plugins/.disabled subdirectory and stay in touch bazaar- vcs.org/ BzrPlugins. Read raw source of this page and parse it. And then user could browse existing plugins and then install them (see above).
2) Install new plugins: from the archive (zip/tar.gz) on local disk or from URL. If this is a branch user could do lightweight checkout of plugin (this simplify update process)
3) Using Plugins Registry from http://