[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 11:56:12 -0400

Greg,
Thanks. I guess the reason for my own confusion (or block headedness)
is that we program in a Windows Environment and have SVN on the LINUX
environment. Now we also do UNIX programming as well but the Repository
and the SVN server is on a LINUX Box.

As your previous email stated about Trunks, branches and tags. That
doesn't match our programming environment. Also I am not the
programmer, I am the administrator that has to set things up.

We are a small IT shop. Myself and a programmer, but we manage a large
system(s) in Windows, COBOL,SCO UNIX and LINUX so you can see (or maybe
not) my problem.

Thanks again for the reply and the help.

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!"

>>> Gregory Garretson <gregory_at_garretson.info> 4/11/2008 10:54 AM >>>
Hi John,

I'm not the expert here, but perhaps if I say something wrong it will
provoke an expert into replying...

As I understand it, you want to create your repository in one
directory,
and then go somewhere else in the filesystem to do the rest of the
steps. Then you can check out a copy of the repository and it won't try

to clobber the actual repository. If you cd to another directory, call

it "temp", you can check out the repository ("repos" or "Calc" or
whatever), which will create an actual subdirectory (the working copy),

into which you can then cd.

As for rm Calc, if you do that with the working copy, it will fail only

because there's something in there. So you need a switch ("rm -r" on
Unix, "rmdir /S" on Windows).

I hope that helps.

Gregory

John BORIS wrote:
> 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
>
>
>

---------------------------------------------------------------------
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 17:57:04 CEST

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