$HOME/.bazaar/plugins Path Not Used by Default

[Tom Browder]

On Sat, Oct 16, 2010 at 02:08, Vincent Ladeuil <v.ladeuil+lp at free.fr> wrote:
>>>>>> Tom Browder <tom.browder at gmail.com> writes:
...
> Thanks for digging this subject !
>
> So, here is the rationale as documented in the code:
>
>    # Ad-Hoc default: core is not overriden by site but user can overrides both
>    # The rationale is that:
>    # - 'site' comes last, because these plugins should always be available and
>    #   are supposed to be in sync with the bzr installed on site.
>    # - 'core' comes before 'site' so that running bzr from sources or a user
>    #   installed version overrides the site version.
>    # - 'user' comes first, because... user is always right.
>    # - the above rules clearly defines which plugin version will be loaded if
>    #   several exist. Yet, it is sometimes desirable to disable some directory
>    #   so that a set of plugins is disabled as once. This can be done via
>    #   -site, -core, -user.
>
> 'site' is not clearly defined across all the platforms, on windows in
> particular we didn't reach an agreement on how it should be implemented
> in the windows installer and even on *nix things are a bit blurry.
>
> But in any case, BZR_PLUGIN_PATH gives full control to the user.
>
> If you can find a better way to describe this in the doc, a patch will
> be be warmly welcome.

Thanks, Vincent, and I'll work on it.

Regards,

-Tom