[MERGE] windows standalone installer creates and uses "plugins" directory for system-wide plugins (#129298)

Aaron Bentley aaron.bentley at utoronto.ca
Sun Nov 25 18:28:35 GMT 2007


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

Alexander Belchenko wrote:
> This patch in the same time bug fix (wishlist-fix actually)
> and improvements. IMO this change is worth to include to 1.0.
> 
> With this patch standalone bzr.exe will able to load plugins
> from C:\Program Files\Bazaar\plugins. This directory will
> be used therefore as location for system-wide plugins.

This brings up an interesting issue for plugins on *nix.

I'm inclined to think we should have standard system plugin paths that
don't depend on the install location of Bazaar itself.

Currently, if Bazaar is installed in /usr, then the plugins directory is
/usr/lib/python*/bzrlib/plugins.  And if Bazaar is installed in
/usr/local, the plugins directory is /usr/local/lib/python*/bzrlib/plugins.

I think we should support loading plugins from either /usr or
/usr/local, though I don't know whether we should define new
directories, or just continue using the existing ones.

Also, we should consider allowing global configuration in /etc

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

iD8DBQFHSb7T0F+nu1YWqI0RAlQsAJ9/1T5nJ7ZYeYqpuRquib+GulRerACgg49h
urkx4FPtq6Pc9mXqsQev8js=
=d9qJ
-----END PGP SIGNATURE-----



More information about the bazaar mailing list