Comment 1 for bug 129298

>Asking on IRC gave me the following answer:
>"put it somewhere else and set the BZR_PLUGIN_PATH env variable", which worked out great, but I think it would be nice if the Windows standalone installer, while it was installing Bazaar, created a Plugins directory in my Bazaar installation directory, and set the environment variable for me.

No, it should not do this.
Windows policy states that applications should not store any settings or configurations files (or any auto-generated files) in Program Files directory. This is our case: each plugin is python sources, and during import Python interpreter will create and save compiled bytecode (*.pyc) files.

Mozilla Firefox and Thunderbird is very good examples of windows applications: their store extensions (== plugins) in

C:\Documents and Settings\%USERNAME%\Application Data\Mozilla\Firefox\Profiles\xxxxx\extensions\
C:\Documents and Settings\%USERNAME%\Application Data\Thunderbird\Profiles\xxxxx\extensions\

Another bad side effect of placing plugins in C:\Program Files\Bazaar\Plugins subdirectory is the fact that uninstaller know nothing about installed plugins and don't know is plugins should be uninstalled or not.

Only one right solution for me (already mentioned in the past, IIRC) is to allow Bazaar looking for plugins in
C:\Documents and Settings\All Users\Application Data\bazaar\2.0\plugins directory in addition to
C:\Documents and Settings\%USERNAME%\Application Data\bazaar\2.0\plugins.

I think this problem could be solved also with some nice GUI tool that allows users explore list of plugins on Bazaar website, download them and install automatically in right location. I started bzr-config application, but plugins support is not implemented yet.

BTW, Mercurial use another approach: their install standalone hg.exe not in C:\Program Files\, but in C:\mercurial instead, and expect plugins in a subdirectory of C:\mercurial.

But actually both approaches have theirs cons and pros.