Re: Multiple repositories with mixed directories (newbie)

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

On Feb 28, 2007, at 15:10, Kylo Ginsberg wrote:

> Fwiw, another idea is to write a checkout script that knows the format
> of your repository, and does non-recursive checkouts of the upper
> directories, followed by a normal recursive checkout of the
> leaf/module directories.   I had to do something like this to get
> support for cvs-style modules with subversion.
>
> Something like:
> #!/bin/bash
>
> mod=$1
> svnroot=svn://server/repos
>
> svn co -N css css
> svn co -N css/modules css/modules
> svn co css/modules/$mod css/modules/$mod

That's not how you're supposed to accomplish that. I was under the  
impression that you have now created, for example, a working copy  
modules which is unrelated to the css working copy containing it, and  
the same for each module.

What I think you want instead is:

svn co -N css css
svn up -N css/modules
svn up css/modules/$mod

That way everything is still seen as a part of the single css working  
copy.


> <repeat for HTML and js in your example below>
>
> A possible downside to this is that the non-recursive checkouts of the
> top directories *will* pull the files in each of those directories.
> YMMV.



-- 

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

Re: Multiple repositories with mixed directories (newbie)

[Kylo Ginsberg <ky...@gmail.com>]

Ah, thanks Ryan!  I hadn't grokked that distinction, but I
experimented a bit.  That makes good sense now.  Thanks,

Kylo

On 2/28/07, Ryan Schmidt <su...@ryandesign.com> wrote:
>
> On Feb 28, 2007, at 15:10, Kylo Ginsberg wrote:
>
> > Fwiw, another idea is to write a checkout script that knows the format
> > of your repository, and does non-recursive checkouts of the upper
> > directories, followed by a normal recursive checkout of the
> > leaf/module directories.   I had to do something like this to get
> > support for cvs-style modules with subversion.
> >
> > Something like:
> > #!/bin/bash
> >
> > mod=$1
> > svnroot=svn://server/repos
> >
> > svn co -N css css
> > svn co -N css/modules css/modules
> > svn co css/modules/$mod css/modules/$mod
>
> That's not how you're supposed to accomplish that. I was under the
> impression that you have now created, for example, a working copy
> modules which is unrelated to the css working copy containing it, and
> the same for each module.
>
> What I think you want instead is:
>
> svn co -N css css
> svn up -N css/modules
> svn up css/modules/$mod
>
> That way everything is still seen as a part of the single css working
> copy.
>

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