Fw: Selective modules checkout

[Fa...@ses-astra.com]

Hello,

I'm trying to make a selective modules checkout. One of the ideas out of it
is to be able to make a "svn update" in the project's root directory to
update the checked out directories only.

Here is the layout of my repository:

REPOS
      trunk
            module1
                  1.1
                  1.3
                  ...
            module2
                  1.1
                  1.3
                  ...
            module3
                  1.1
                  1.3
                  ...
      branches
            module1
                  1.0
                  1.2
                  ...
            module2
                  1.0
                  1.2
                  ...
            module3
                  1.0
                  1.2
                  ...

Because I don't require all the modules and because module3 for instance is
quite huge (200MB), what I am trying to do is to checkout only module1 and
module2 and ignore module3.

With the command-line Subversion client, I found a 3 steps approach, which
is the following:

1. Checkout the base branch (for instance 'trunk') to make it the project's
root directory

      svn checkout -N svn+ssh:///<repos_url>/trunk <project_name>

2. Step into the newly checked out root directory and checkout the required
modules;

      cd <project_name>
      svn checkout svn+ssh:///<repos_url>/trunk/module1
      svn checkout svn+ssh:///<repos_url>/trunk/module2

At this step, the "svn update" command works as I require (only the checked
out modules are updated), but after a "svn cleanup" the "svn update"
command gets the missing modules (module3 in the example above).

The questions are: Is it the right way to proceed? Is there any other
better alternative? Any future feature in Subversion that will do it?

Regards,
Fabien.

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

Re: Selective modules checkout

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

On Feb 14, 2007, at 03:13, Fabien.Bouleau@ses-astra.com wrote:

> I'm trying to make a selective modules checkout. One of the ideas  
> out of it
> is to be able to make a "svn update" in the project's root  
> directory to
> update the checked out directories only.
>
> Here is the layout of my repository:
>
> REPOS
>       trunk
>             module1
>                   1.1
>                   1.3
>                   ...
>             module2
>                   1.1
>                   1.3
>                   ...
>             module3
>                   1.1
>                   1.3
>                   ...
>       branches
>             module1
>                   1.0
>                   1.2
>                   ...
>             module2
>                   1.0
>                   1.2
>                   ...
>             module3
>                   1.0
>                   1.2
>                   ...
>
> Because I don't require all the modules and because module3 for  
> instance is
> quite huge (200MB), what I am trying to do is to checkout only  
> module1 and
> module2 and ignore module3.
>
> With the command-line Subversion client, I found a 3 steps  
> approach, which
> is the following:
>
> 1. Checkout the base branch (for instance 'trunk') to make it the  
> project's
> root directory
>
>       svn checkout -N svn+ssh:///<repos_url>/trunk <project_name>
>
> 2. Step into the newly checked out root directory and checkout the  
> required
> modules;
>
>       cd <project_name>
>       svn checkout svn+ssh:///<repos_url>/trunk/module1
>       svn checkout svn+ssh:///<repos_url>/trunk/module2

Now, module1 and module2 are completely disconnected from the trunk  
they're in. That's probably not what you want. Instead, you probably  
want this:

cd <project_name>
svn up module1 module2


> At this step, the "svn update" command works as I require (only the  
> checked
> out modules are updated), but after a "svn cleanup" the "svn update"
> command gets the missing modules (module3 in the example above).

If you don't want the entire contents of trunk, don't do "svn up" in  
the trunk. Just say "svn up module1 module2" and whatever else you do  
want to update.


> The questions are: Is it the right way to proceed? Is there any other
> better alternative? Any future feature in Subversion that will do it?

FYI, the "svn co -N" feature is a bit broken; not sure if it'll be  
fixed anytime soon. This is the bug:

http://subversion.tigris.org/issues/show_bug.cgi?id=695


-- 

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