Basic Q: one tag for different paths?

[Kynn Jones <ky...@gmail.com>]

I'm new to revision control, and have a very basic question.

I have a project whose files live under different directory trees,
something like

/opt/lib/perl5/MyProject
/www/cgi/myproject
/www/docroot/javascript/myproject
/www/docroot/icons/myproject

So I want to have the same directory structure under MyProject/trunk
in the repository, i.e.:

MyProject/trunk/opt/lib/perl5/MyProject
MyProject/trunk/www/cgi/myproject
MyProject/trunk/www/docroot/javascript/myproject
MyProject/trunk/www/docroot/icons/myproject

OK now, let's assume that we have this, and that I have already
populated these repository directory with files.  Also, let's assume
that I'm working on a Unix system, and that my current filesystem
already has the directories

/opt/lib/perl5
/www/cgi
/www/docroot/javascript
/www/docroot/icons/

...possibly containing other files, unrelated to my project.

My question is: how would I go about setting a working environment
from the files that are archived under MyProject/trunk in the
repository?

Would I need to separately cd to each directory in the working
environment (/opt/lib/perl5, /www/cgi, etc.) and execute "svn update"
(or "svn checkout")?  Or is it possible to achieve the same effect
with a single svn command?

Thanks in advance!

kj

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Basic Q: one tag for different paths?

[Ryan Schmidt <su...@ryandesign.com>]

On Feb 24, 2007, at 10:25, Kynn Jones wrote:

> I'm new to revision control, and have a very basic question.
>
> I have a project whose files live under different directory trees,
> something like
>
> /opt/lib/perl5/MyProject
> /www/cgi/myproject
> /www/docroot/javascript/myproject
> /www/docroot/icons/myproject
>
> So I want to have the same directory structure under MyProject/trunk
> in the repository, i.e.:
>
> MyProject/trunk/opt/lib/perl5/MyProject
> MyProject/trunk/www/cgi/myproject
> MyProject/trunk/www/docroot/javascript/myproject
> MyProject/trunk/www/docroot/icons/myproject
>
> OK now, let's assume that we have this, and that I have already
> populated these repository directory with files.  Also, let's assume
> that I'm working on a Unix system, and that my current filesystem
> already has the directories
>
> /opt/lib/perl5
> /www/cgi
> /www/docroot/javascript
> /www/docroot/icons/
>
> ...possibly containing other files, unrelated to my project.
>
> My question is: how would I go about setting a working environment
> from the files that are archived under MyProject/trunk in the
> repository?
>
> Would I need to separately cd to each directory in the working
> environment (/opt/lib/perl5, /www/cgi, etc.) and execute "svn update"
> (or "svn checkout")?  Or is it possible to achieve the same effect
> with a single svn command?

It would probably be better to have the following structure in your  
repository:

MyProject/
	trunk/
		perl5/
		cgi/
		javascript/
		icons/

You can check out the trunk of your project anywhere on disk that you  
like. Then, make symlinks from all the other places (/opt/lib/perl5/ 
MyProject, /www/cgi/myproject, etc.) to the correct parts of this  
single working copy. Then it's easy to update everything by just  
updating the working copy.


-- 

To reply to the mailing list, please use your mailer's Reply To All  
function


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org