You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Phil Lawrence <pr...@Lehigh.EDU> on 2005/06/07 20:48:49 UTC
check out on top of existing tree
How can I checkout ON TOP OF 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 $VENDOR_HOME
$ 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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: check out on top of existing tree
Posted by kf...@collab.net.
Phil Lawrence <pr...@Lehigh.EDU> writes:
> > 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:
> > http://subversion.tigris.org/faq.html#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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: check out on top of existing tree
Posted by Phil Lawrence <pr...@Lehigh.EDU>.
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:
>
> http://subversion.tigris.org/faq.html#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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: check out on top of existing tree
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jun 8, 2005, at 2:34 AM, Max Bowsher wrote:
> Phil Lawrence wrote:
>
>> How can I checkout ON TOP OF 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 $VENDOR_HOME
>> $ 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:
http://subversion.tigris.org/faq.html#in-place-import
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: check out on top of existing tree
Posted by Saulius Grazulis <gr...@ibt.lt>.
On Wednesday 08 June 2005 12:34, Max Bowsher wrote:
> > Now, how do I checkout on top of the full vendor tree?
> > $ cd $VENDOR_HOME
> > $ 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.
I think you can just remove the original foo (I mean, move it to a safe
place ;) and check out the versioned copy:
mv foo foo-DIST
svn co https://.../vendor/trunk/foo
Later on, you can update:
svn update
should refresh just the versioned files.
If you commit from the vendor tree as well, you may want to add all other
files to the svn ignore property, so that they do not pop up with question
marks all the time.
--
Dr. Saulius Grazulis
Institute of Biotechnology
Graiciuno 8
LT-02241 Vilnius
Lietuva (Lithuania)
fax: (+370-5)-2602116
tel.: office: (+370-5)-2602556
mobile: (+370-684)-49802, (+370-614)-36366
Re: check out on top of existing tree
Posted by Max Bowsher <ma...@ukf.net>.
Phil Lawrence wrote:
> How can I checkout ON TOP OF 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 $VENDOR_HOME
> $ 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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org