That seems to have worked out. If anyone's interested, three patches: - One on TracMonotone: http://tracmtn.1erlei.de/attachment/ticket/13/tracmtn-65cc6f.patch - One on Trac, multirepos branch: http://trac.edgewall.org/attachment/ticket/7920/trac-multirepos-r7684.patch - One on Bitten, experimental/trac-0.11 branch: http://bitten.edgewall.org/attachment/ticket/342/bitten-trac0.11-r571.patch
The TracMonotone patch changes TracMonotone, so that each separate repo can include a monotone selector to e.g. select a single branch. On Dec 29, 9:27 pm, Noah Kantrowitz <[email protected]> wrote: > The new multi-repo APIs should help to alleviate this. Currently Trac > doesn't really grok the idea of having more than one "code base" in a > single Trac. I know the branch has a version of the svn and hg > plugins, you might want to try adding support to the mtn plugin as > well. You would probably also need to put a repo selector (assuming > you manifest branches as isolated repos) into bitten. Hope that helps. > > --Noah > > On Dec 28, 2008, at 12:24 PM, Cider head wrote: > > > > > Hey, are there many trac users who use the monotone backend out there? > > I've been playing around with Trac, Bitten and TracMtn, and the whole > > lot doesn't quite hang together. > > > Trac and TracMtn seem to work together fairly well. It's a bit > > arbitrary which revision turns up in the browser when you hit 'Browse > > source', and the Timeline view wants to display every revision in the > > repository. It's not possible to convince the timeline to only display > > certain branches (as far as I can see). > > > Bitten seems to have a similar view of the monotone repository: By > > default, it just tests the latest revision regardless of which branch > > it's on. The 'Build all revisions' option under Master Settings will > > get it to try to build and test every single revision regardless of > > which branch the revision is on. I guess this isn't going to work for > > most people, since most repositories will contain multiple projects, > > differentiated by the branch name. > > > I'm thinking that the current versioncontrol API is centred around > > subversion. I'm not sure the whole Node concept is a good match for > > monotone, judging by the methods it supports. > > > So, I've been playing with the code a bit. Just to experiment, I > > introduced a RepositoryView object which is like the existing > > Repository, but it restricts the view according to some selector like > > branch or tag, and the actual selector can be specified in the config > > file. The bulk of the changes are on the versioncontrol API, with some > > small changes in Bitten and TracMtn. > > > So, I'm interested to know... > > - Is there any refactoring on the VC API going on at the moment? Is it > > something that needs some help? > > - Is anyone using trac with montone? Would they be interested in my > > patches (~300 lines of patch). Where should I post this stuff? > > - If there's some development going on that needs assistance, let me > > know. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
