Proposal for plugin management UI

[Matthieu Moy]

"Michael Ellerman" <michael at ellerman.id.au> writes:

> Mmmm, I think that's a little over engineered for what we really need.

I also think so.

> As I see it there's two classes of users:
>  - The Eriks, who want to run bleeding edge plugins, and manage them by hand.
>  - The Wouters, who just want what works, and want it now!
>
> The first class I think is served quite well by the current system,
> they just cd into ~/.bazaar/plugins and branch from the plugin's URL.
> Not too hard.

Indeed, a good nested trees support would make this even easier.

Suppose, developers X, Y and Z have their own plugin.

Aaron makes X, Y and Z subtrees of bzrtools. Then, with one command, a
user can branch bzrtools and its subtrees. Now, if one more plugin
gets added, say W, a "bzr pull" should also branch W.

And for sure, if users want X, Y, Z and W individually, they are
welcome to do so.

-- 
Matthieu