#2086: better support for multiple repositories
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 0.11
Component: browser | Version: devel
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by anonymous):
SVN supports multiple branches per Repository. Darcs does not.
Trac is expected to provide a whole project view with multiple branches.
So it should (I would say needs to) implement this via multiple repos for
the darcs plugin. The one repo restriction of Trac only makes sense with
One Repo/Multiple Branches SCMSs like subversion.
For implementation, maybe just require darcs repos to live somewhere below
a common base dir, and look for branch dirs (which are also proper darcs
repos on their own, sharing some common revision in the past) recursively
by looking for the _darcs subdir. The path from base to the repo/branch
dir could be mapped to the branch name. That way, you might not need to
store extra data (in core or whatever) about multiple repos, just append
the branch name to the base dir to get the real repo dir whenever
accessing a branch.
I have not looked at Trac code yet, I don't know how hard this would be,
but this is kind of a "must have" for serious Trac deployment here. Not
having it means Trac+Darcs is crippled in comparison to Trac+SVN.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2086>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
