want configuration items to disable/enable plugins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Vincent Ladeuil |
Bug Description
In thread "Windows packaging/
2009/8/10 Alexander Belchenko <email address hidden>:
I'd like to have more fine grained control on what plugins are
it from plugins folder. It has its own pros and cons, but it's definitely
(little) problem if you want to keep your plugins base lean to avoid longer
startup time of bzr.
I was thinking about this too, in testing things in 2a. How about
just a crude configuration option to block out named plugins?
INMHO, plugins section in bazaar.conf will be nice:
[PLUGINS]
bzrtools = enable
svn = disable
If plugin is not mentioned in this section assume it's enabled as it works now.
Related branches
- Vincent Ladeuil: Approve
-
Diff: 31 lines (+4/-4)2 files modifiedbzrlib/lazy_regex.py (+3/-3)
doc/en/release-notes/bzr-2.7.txt (+1/-1)
Changed in bzr: | |
milestone: | none → 2.2b1 |
status: | In Progress → Fix Released |
Please consider making it based on the directory name instead of the plugin name so that it can also be used to allow testing various branches of the same plugin.
Of course a single directory can be allowed for a given plugin and there may be some trickery involved when mapping the directory to the python namespace (I'm not familiar with the plugin loading code so I may be wrong).