How can I checkout N TP F an existing dir structure?
Usage:
We have a *very* large vendor tree on a production server. I only want
to version a few files within it. So I copy the stuff I want into a
sparse version of the vendor tree, and import. No problem.
Now, how do I checkout on top of the full vendor tree?
$ cd $VENDR_HME
$ svn checkout https:///vendor/trunk .
svn: Failed to add directory 'foo': object of the same name already exists
What's the right way to do this?
Phil
To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

Phil Lawrence wrote:
How can I checkout N TP F an existing dir structure?

Usage:
We have a *very* large vendor tree on a production server. I only want
to version a few files within it. So I copy the stuff I want into a
sparse version of the vendor tree, and import. No problem.

Now, how do I checkout on top of the full vendor tree?
$ cd $VENDR_HME
$ svn checkout https:///vendor/trunk .
svn: Failed to add directory 'foo': object of the same name already exists

What's the right way to do this?

I'm not actually aware of any convenient way to do this. I think perhaps
this is a missing feature.

Max.

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

Jun 8, 2005, at 2:34 AM, Max Bowsher wrote:

Phil Lawrence wrote:
>
>How can I checkout N TP F an existing dir structure?
>>
>Usage:
>We have a *very* large vendor tree on a production server. I only
>want
>to version a few files within it. So I copy the stuff I want into a
>sparse version of the vendor tree, and import. No problem.
>>
>Now, how do I checkout on top of the full vendor tree?
>$ cd $VENDR_HME
>$ svn checkout https:///vendor/trunk .
>svn: Failed to add directory 'foo': object of the same name
>already exists
>>
>What's the right way to do this?
>>
>
I'm not actually aware of any convenient way to do this. I think
perhaps this is a missing feature.

The usual workaround for this scenario is the 'in-place' import
technique, because it doesn't require a checkout after things are
committed to the repository:

#in-place-import

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

Ben Collins-Sussman wrote:

The usual workaround for this scenario is the 'in-place' import
technique, because it doesn't require a checkout after things are
committed to the repository:

#in-place-import

The example given there is very apt because it demonstrates the
exact problem I am having. If I want to import just some of my /etc, I
can use the referenced method to do so *in place*. Very nice.

But when I go to check out that nicely versioned bit of /etc on another
box, I immediately run into the problem:
svn: Failed to add : object of the same name already exists

You see the problem? I want to overlay the current head on an existing
directory.

Phil

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

Phil Lawrence <prlawrence (AT) Lehigh (DOT) EDUwrites:
The usual workaround for this scenario is the 'in-place' import
technique, because it doesn't require a checkout after things are
committed to the repository:
#in-place-import

The example given there is very apt because it demonstrates the
exact problem I am having. If I want to import just some of my /etc,
I can use the referenced method to do so *in place*. Very nice.

But when I go to check out that nicely versioned bit of /etc on
another box, I immediately run into the problem:
svn: Failed to add : object of the same name already exists

You see the problem? I want to overlay the current head on an
existing directory.

Yup. I think Max is right, this is a missing feature. If you'd like
to file an enhancement issue on it, that would be great. Just make
sure to point to this mail thread from the issue. No promises about
when it would get implemented (a patch makes it happen faster, of
course), but at least an issue gives us a canonical place to gather
information. The description of the feature seems pretty simple and
self-contained, which is good.
-Karl

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org