[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: trunk directory question from a CVS guy

From: Talden <talden_at_gmail.com>
Date: 2007-05-08 11:11:07 CEST

CVS example

projectX/
  src/
  etc/

In CVS, when you check out module 'projectX', you get a working copy
rooted at projectX (assuming you didn't "cvs co -d blah projectX")

Because subversions 'trunk', branches and tags are simply paths in the
repository you would have a repository layout something similar to
what Irvine suggested...

projectX/
  trunk/
    src/
    etc/
  branches/
    br1/
    ...
  tags/
    t1/
    ...

To get a working copy the same as with CVS, do as Irvine notes and use
the Subversion equivalent of the CVS -d checkout option

Something like
  svn co svn:..../projectX/trunk projectX

Reorganisation of our CVS projects to best fit Subversion is first
order of business... There's no question it's needed, but then I don't
think there's much question that it'll be worth it. Many a repository
tidy-up has been put off until later due to CVS limitations.

This approach to branches and tags is definitely different and I'm
disappointed there isn't a little more built into the tool to assist
with this, but I'm yet to see it as a limitation or a hinderence.

--
Talden
On 5/8/07, Irvine, Chuck R [EQ] <Chuck.R.Irvine@embarq.com> wrote:
> The convention is that "trunk" should be your top level project
> directory. Eg:
>
> Repo/
>         trunk/
>                 src/
>                 etc/
>         branches/
>                 br1/
>                         src/
>                         etc/
>                 br2/
>                         src/
>                         etc
>
> From what you say below, though you don't really say, I'm guessing you
> have something like:
>
> Repo/
>         /application
>                 trunk/
>                 br1/
>
> And you are checking out at the "application" level. What you normally
> do instead is check out either "trunk", "br1", or "br2". Note that the
> name given to your top level directory upon checkout is configurable.
>
> > -----Original Message-----
> > From: Ennis, Tony [mailto:TEnnis@comdata.com]
> > Sent: Thursday, May 03, 2007 8:34 AM
> > To: 'users@subversion.tigris.org'
> > Subject: trunk directory question from a CVS guy
> >
> >
> > I am setting up my first SVN repository. I see in a lot of
> > the docs that the SVN community recommends a "trunk"
> > directory where the main line of the code lives.  As per some
> > 'how to be a newb' instructions, I created /trunk and
> > imported my pre-existing java project into it.
> >
> > I created a new project from using Subclipse.  Within
> > Eclipse, the project now included a folder called "trunk"
> > which contained all my files.  Now I can see how this would
> > happen, but is it normal in svn-managed projects to have the
> > trunk directory in the project?  Checking out from CVS
> > doesn't create a folder called HEAD.
> >
> > It was trivial to get the app to compile and for the junit
> > tests to go green so I know my project isn't too broken.
> >
> >
> > -----------------------------------------
> > IMPORTANT: The sender intends that this electronic message is
> > for the exclusive use of the person to whom it is addressed.
> > This message may contain information that is confidential. If
> > the reader of this message is not an intended recipient, be
> > aware that any disclosure, dissemination, distribution or
> > copying of this communication, or the use of its contents, is
> > prohibited. If you have received this message in error, then
> > please immediately notify the sender of your inadvertent
> > receipt and delete this message from all data storage
> > systems. Thank you.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 8 11:11:31 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.