Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by dagolden (6584) on 2007.03.21 6:24 (#53913) Journal

    While it's a different situation, when I was setting up my CPAN repository on googlecode, what I thought about was how I (or others) would use SVK to work with the code. What parts of the repository would I mirror locally?

    Putting the trunk too high up would mean I'd be mirroring everything or else having to separately mirror a trunk, tags, and branches if I only wanted to work on a single module.

      /svn/trunk/{module-A|module-B|...}
      /svn/tags/{module-A|module-B|...}
      /svn/branches/{module-A|module-B|...}

    So, better for me was a module-first layout

      /svn/module-A/{trunk|tags|branches}
      /svn/module-B/{trunk|tags|branches}
      ...

    Given your description, the lowest pain structure for your teams is probably team centric, but with the possibility of merging to a common point over time.

      /svn/alpha/{trunk|tags|branches}
      /svn/beta/{trunk|tags|branches}
      /svn/gamma/{trunk|tags|branches}
      /svn/common/{trunk|tags|branches}

    I also like the suggestion above to be module-centric but disambiguate by team name.

      /svn/Module-Foo-alpha/{trunk|tags|branches}
      /svn/Module-Foo-beta/{trunk|tags|branches}
      /svn/Module-Bar-gamma/{trunk|tags|branches}
      ...

    As modules are renamed to be uniquely named, that's easy to change. (Hooray for Subversion directory renames).

    -- xdg