Lele Gaifax wrote:
Christian Boos ha scritto:
But maybe the "namespace_packages" functionality of setuptools could
help here, suggesting a policy of using a common
"trac.versioncontrol" namespace for all the plugins.
Thanks for the tip.
I implemented this in http://projects.edgewall.com/trac/
Christian Boos ha scritto:
But maybe the "namespace_packages" functionality of setuptools could
help here, suggesting a policy of using a common "trac.versioncontrol"
namespace for all the plugins.
Thanks for the tip.
I implemented this in http://projects.edgewall.com/trac/changeset/2897
Gre
Lele Gaifax wrote:
Christian Boos ha scritto:
E.g. currently, if I set the repository_type to hg,
I have to edit trac.ini and add:
[components]
hgtrac.* = enabled
It would be better if initenv would do it for me:
[components]
trac.versioncontrol..* = enabled
Yes, I think that would be bette
Christian Boos ha scritto:
E.g. currently, if I set the repository_type to hg,
I have to edit trac.ini and add:
[components]
hgtrac.* = enabled
It would be better if initenv would do it for me:
[components]
trac.versioncontrol..* = enabled
Yes, I think that would be better: for my tracdarcs
Hi,
I think we should come up with a convention for naming the vc backend
plugins.
That way, after an initenv, we could directly enable the component in
the trac.ini,
only by knowing the repository_type.
E.g. currently, if I set the repository_type to hg,
I have to edit trac.ini and add:
[co
