On Tue, Mar 25, 2008 at 12:16 PM, Todd Nine <todd.nine_at_gmail.com> wrote:
> I've found that my repository administration/setup depends greatly on my
> projects. I primarily use maven/java for builds, but this seems to hold
> true for my Ruby and C++ projects as well. If I have multiple modules to a
> release, and they are all tagged/released at once, I use the following
> structure
>
> trunk/moduleA
> trunk/moduleB
> trunk/moduleC
>
>
> This way, I can tag all modules in the tags directory.
>
> If I release each project individually, I have this setup
>
> moduleA/trunk
> moduleA/branches
> moduleA/tags
>
>
> moduleB/trunk
> moduleB/branches
> moduleB/tags
>
> Then I can tag each module individually.
>
> Hopefully this helps. Obviously the source is imported to the end of the
> path for my above examples.
>
>
> On Tue, Mar 25, 2008 at 12:00 PM, Charles Villa <CVilla_at_tekscan.com>
> wrote:
>
> > I'm sure this question has been asked thousands of times, but after
> > reading the faqs and the book I'm still not clear.
> >
> > It seems that common convention is to use the subdirectrories, trunk,
> > branches and tags. What I'm confused is where to put the first import? The
> > examples show it going into repos/project, not repos/project/trunk. I think
> > I should not be placing anything in the project's root if I am using the
> > subdirectory layout, but I'd like to be sure.
> >
> > Also, what are people's views with multiple projects? I'm trying to
> > decide between one repository per project and multiple projects per
> > repository. Do you generally find the global revision number bump more
> > irritating than having to do svnadmin to create a new repo?
> >
> > Thanks,
> > Charles Villa
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> > For additional commands, e-mail: users-help_at_subversion.tigris.org
> >
> >
>
Received on 2008-03-25 01:07:06 CET