Am 01.03.2006 um 19:10 schrieb Christian Boos:
Christopher Lenz wrote:
Am 01.03.2006 um 17:19 schrieb Christian Boos:
Christian Boos wrote:
...
In addition to the above, I added the trac.versioncontrol namespace,
which ease the integration of vc backend plugins.
I'm -1 on this change, at least at this point.
The trac package is currently assumed to contain only the official
Trac modules, which are by default all enabled in the component
system. When we start opening up the package for third-party
extensions, those extensions become (rather unexpectedly) enabled
by default. Thus the distinction between built-in components and
plugins becomes blurred, or rather, the heuristics for when
plugins are enabled become less intuitive.
I see. However, we still need a way to disable the svn backend when
it's not
the default, and I think it's good to automatically enable the vc-
backend plugin
corresponding to the selected repository type during initenv.
The first point is easy to do, the second is just a matter of
convention.
I'm ok to not use the trac package for the reasons you mentioned,
but let's find another name, e.g. <repos_type>_trac or
tracvc.<repos_type> ...
Oops, forgot to follow up on this...
I'm -1 on *any* kind of auto-enabling of external plugins, no matter
what namespace. I just don't think it's worth the potential confusion.
As an additional perspective, I see initenv changing radically for
0.11, and I think we discussed this before. All the current required
arguments would become options, and you could simply initenv a path
and be done. Then, you either go in trac.ini and start editing, or
you start the web-app and use WebAdmin to setup up stuff like plugins
and the repository.
Cheers,
Chris
--
Christopher Lenz
cmlenz at gmx.de
http://www.cmlenz.net/
_______________________________________________
Trac-dev mailing list
Trac-dev@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-dev
