rethinking the plugin load order change
John Arbash Meinel
john at arbash-meinel.com
Thu Mar 8 21:46:13 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Robert Collins wrote:
> On Thu, 2007-03-08 at 11:01 -0600, John Arbash Meinel wrote:
>> One argument might be to have a default site location for plugins,
>> rather than /usr/lib/python2.4/site-packages/bzrlib/plugins/*
>> And then it could be a 3-tier. Load from bzrlib/plugins, then from user,
>> then from site-wide.
>> At the moment, though we only have 2 locations, so bzrlib/plugins should
>> be underneath user plugins. Otherwise users have no way to override site
>> installed plugins.
> Yes, this is something I thought I suggested before: it solves several
> - this one
> - uninstalling bzr without affecting 3rd party installed plugins
> - 3rd party plugins that get moved into core will stop overwriting the
> bzr copy on disk when they are installed.
> I'm +1 on this.
So what do you recommend as the default path? To me this seems a lot
like a 'compiled in default' that other programs use. So you pass it as
a parameter to the 'configure' script.
Bzr doesn't really have the same 'configure' step that other programs have.
I suppose one possibility would be 'bzrplugins' so something like
which sits *next* to bzrlib rather than underneath it.
Then at runtime we find it by just running 'import bzrplugins; path =
dirname(bzrplugins.__file__)' or something like that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar