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

[Alexander Belchenko]

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

Aaron Bentley пишет:
> 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.

Probably you mean: /usr/lib/python*/site-packages/bzrlib/plugins
and corresponding path for /usr/local.
Actually similar path used for python-based installation
on Windows, i.e.
C:\Python*\Lib\site-packages\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 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHSceTzYr338mxwCURAhtUAJ40/CQOlWmQa7LuGXJY73PW+S+tWgCeOZGo
apBDFeu0ESS6MH6k/sZgeCM=
=PiMR
-----END PGP SIGNATURE-----