[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: Duncan Murdoch <murdoch_at_stats.uwo.ca>
Date: 2007-05-03 16:44:44 CEST

On 5/3/2007 10:28 AM, Ennis, Tony wrote:
> (Sorry if this is a double-post, I jumped the gun on submitting when
> I joined)
>> 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.
> I don't care too much if 'trunk/' is there or not, I just want to do
> it the standard and accepted way.
>> 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.

If you create a repository for a project named Proj, then typically
you'd access the trunk using the URL


(or maybe some other access method, like https, svn+ssh, etc.)

When you check it out, you normally only check out this much from the
repository, and you don't need to call the checkout "trunk". You can
call it whatever you like. So the name "trunk" needn't show up in a
working copy's local path. It will always be mentioned in the
associated URL, but you rarely need to type that after checkout.

I hope this helps.

Duncan Murdoch

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 3 16:44:13 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.