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

Alexander Belchenko bialix at ukr.net
Wed Nov 28 22:25:00 GMT 2007


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

Robert Collins пишет:
> Robert Collins has voted approve.
> Status is now: Approved
> Comment:
> I think this is ok, however it's a bit strange that setting the plugin
> path by hand will remove the system wide plugins directory; thats not
> how it works on linux. If you have time I'd rather see you always append
> the system wide location (which is bzrlib's own plugins dir on linux)
> rather than only apply if if the user hasn't supplied their own path.
> 
> I suggest this so that bzr will behave the same on windows and linux
> when a user does BZR_PLUGIN_PATH=XXX

Hmm. Interesting.
I'm thinking about BZR_PLUGIN_PATH and its masking effect, but...

May I go a bit further and ask provoking question?

May be we should move standard built-in plugins (err, very funny pun indeed)
[I mean launchpad and multiparent] into this system-wide directory as well
and simply disable our load-plugins-from-zip support?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHTeq8zYr338mxwCURArK9AJ95rz/D/KnoQhvwhFKYRQzKZbfJJQCfVTUQ
3hLYImdMLrsb5vVqz749H7g=
=Haho
-----END PGP SIGNATURE-----



More information about the bazaar mailing list