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

RE: How to set up project directories--SVN book confusion

From: John BORIS <jboris_at_adphila.org>
Date: Fri, 11 Apr 2008 10:22:55 -0400

I have a question concerning the steps below. As i am new to this as
well and just as confused. The line rm <repo> is that correct? If I
substituted Calc for repo line 1 would be:

svnadmin create Calc

but if I do a cd Calc , wouldn't that fail? as would rm Calc.

Sorry to be dense on this.

John J. Boris, Sr.
JEN-A-SyS Administrator
Archdiocese of Philadelphia

"Remember! That light at the end of the tunnel
Just might be the headlight of an oncoming train!"

>>> <nicklist_at_planet.nl> 4/11/2008 8:13 AM >>>
Basicly it would be something like:

svnadmin create <repo>

svn co file://<repo>
cd <repo>
svn mkdir trunk
svn mkdir branches
svn mkdir tags
svn ci -m "Initial layout"
rm <repo>

svn co <repo>/trunk <repo>
cd <repo>

And you'll have a checkout of the trunk.

This assumes one trunk/branches/tags setup per repository, the more
common layout would be multiple trunk/branches/tags setups per
repository.

So, repository layout would be:

<repository>
   <project-a>
        trunk
        branches
        tags
   <project-b>
        trunk
        branches
        tags

etc, etc, etc. I guess you can figure out how to setup such a
repository following the instructions in the first part of the mail.
(Hint: use svn mkdir <project-a> )

Hth,

Nick S.

-----Original Message-----
From: Gregory Garretson [mailto:gregory_at_garretson.info]
Sent: Fri 4/11/2008 13:55
To: users_at_subversion.tigris.org
Subject: How to set up project directories--SVN book confusion
 
I'm just getting started with Subversion, so please pardon this
low-level question. I've read the Subversion book, which is generally
excellent, but it has caused me to be confused about how to set up a
project.

In Chapter 5 on "Repository Administration", the book talks about the
virtual filesystem in which data is stored. Then it goes on to discuss

"directory hierarchies within the repositories themselves", and how you

might want to set up your repository, with trunk, branch, and tags
directories. What is not made clear is whether these are (a)
directories
in the svn virtual filesystem, or (b) directories in the actual OS
filesystem (prior to checkout).

If they are intended to really be OS directories, the description is
very misleading, since it doesn't say where these should be in relation

to all the other files in the repository, or whether you're meant to
set
them up elsewhere in the filesystem.

If they are intended to be directories in the virtual filesystem, there

is no dicussion of how to go about creating them. Going back to Chapter

2, "Basic Usage", there is a section called "Recommended repository
layout", which is a summary of what is said in Chapter 5 and sends you

back there for further information. Then it goes on to tell you how to

do a checkout, which presupposes that the repository has already been
set up. There is a section on importing into a repository, but it
doesn't respect the trunk-branches-tags advice given in the following
section, so it's hard to see how those relate to each other.

So, as briefly as I can phrase it, here is my question: What is the
proper way to create from scratch an svn project using the
trunk-branches-tags setup?

Maybe I've missed something rather obvious. That's certainly possible;

if so, please let me know.

Thanks,
Gregory

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-11 16:23:27 CEST

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.