install-plugin command?

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).

and 4) update plugins if it checkouts.

I agree with Alexander's comments, I had written some very similar notes
a few minutes ago. Here are some other thoughts on how this could work:

- when updating the plugins, have the ability to update to a tag rather
than always updating to the tip.
- in addition to searching the well-known public plugin registry, have
the ability to configure additional locations to be checked for plugins
(this would be useful for site-specific plugins, for example if a
developer on a project was required to install some project specific plugin)

cheers,
-elliot

I would recommend moving the file to plugins/DISABLED rather than plugins/.disabled.

It isn't a big thing, but you don't really need to hide them, just move them 1 level deeper. To me, all caps makes it just as obvious that it is a special directory, and means that people can find it (it isn't hidden by default).

This is starting to sound a lot like 'apt for plugins'. And I think keeping in mind that we are looking for a remote registry which contains references we can update from, means that we can create something that does more than just update plugins.

In a sense, Launchpad is meant to/should be designed to do a lot of that. But that doesn't mean it wouldn't be nice to have support for 3rd party registries.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A Meinel пишет:
> I would recommend moving the file to plugins/DISABLED rather than
> plugins/.disabled.
>
> It isn't a big thing, but you don't really need to hide them, just move
> them 1 level deeper. To me, all caps makes it just as obvious that it is
> a special directory, and means that people can find it (it isn't hidden
> by default).

OK. I'm was unsure about .disabled, so if you think it worth to don't use
hidden directory -- I'm agree. This should be just some predefined directory.
Just for case to not configure its name.

- --
Alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFuN6tzYr338mxwCURAg05AJ4idJtO33p4820lpxsmPUHz5xvCagCeJa3J
LU45rc0hb7VmL8oZlZTYy3Q=
=Ycwp
-----END PGP SIGNATURE-----

On Thu, Jan 25, 2007 at 04:09:34PM -0000, John A Meinel wrote:
> I would recommend moving the file to plugins/DISABLED rather than
> plugins/.disabled.

plugins/DISABLED is also what I've been using.

> It isn't a big thing, but you don't really need to hide them, just move
> them 1 level deeper. To me, all caps makes it just as obvious that it is
> a special directory, and means that people can find it (it isn't hidden
> by default).
>
>
> This is starting to sound a lot like 'apt for plugins'. And I think
> keeping in mind that we are looking for a remote registry which
> contains references we can update from, means that we can create
> something that does more than just update plugins.

I'm uncomfortable duplicating package managers work. But if people want
to build it I'm not going to stop them. Thinking in that direction
though, a --system option or such to make it available for more than one
user, but writing in a package management controlled dir would meet my
objection.

Wouter van Heyst

I actually use plugins/DEACTIVATED, but it is the same idea.

The problem with "duplicating package managers work" is that they aren't going to give you the latest revision. Or really give you a way to get the Bazaar branch of a project.

So it isn't 100% the same as a package manager. But it is a "branch manager".

Maybe when Ubuntu finally implements:
  https://wiki.ubuntu.com/NoMoreSourcePackages

Then we won't need it anymore.

Hello,
what is the status of this install utility?

Why not using a setuptools/easy_install like approach?

One would package all plugins and provide an interface to easyinstall.

Looking forward to hear from you.