[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: copy newly added file

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Fri, 31 Jul 2009 14:36:18 -0500

On Jul 31, 2009, at 01:28, FEJES Jozsef wrote:

> Yes, I didn't the know the correct phrase but cheap copies are exactly
> what I want. So, as an example, let's say we have two class
> libraries A
> and B, and two web projects, C and D. When compiling, we get an
> A.dll, a
> B.dll, and the web pages compile into a directory structure. We would
> like to publish this entire thing in one transaction like this:
> tags\1.2.3.4\lib\A.dll
> tags\1.2.3.4\lib\B.dll
> tags\1.2.3.4\webC\stuff
> tags\1.2.3.4\webC\bin\webC.dll
> tags\1.2.3.4\webC\bin\A.dll [+]
> tags\1.2.3.4\webD\stuff
> tags\1.2.3.4\webC\bin\webD.dll
> tags\1.2.3.4\webD\bin\A.dll [+]
> tags\1.2.3.4\webD\bin\B.dll [+]
> Where the marked files shouild be cheap copies from lib. Externals are
> no good either because we require that all dll's be in the same
> directory. I know there are many places to workaround this issue,
> but it
> would be really easier this way.
>
> So let's forget my previous terminology, my new question is: if I
> copy a
> file not yet committed, is that a cheap copy or not?
>
>>> I know that a newly added file doesn't have a history yet but why
>>> does
>>> that matter? That + sign could appear just like it does with another
>>> file that does have a history, it should be a link nonetheless. I
>>> don't
>>
>> Well the + means "copied with history", but clearly from svn's
>> perspective there is no history, so I think the output is correct. I
>> don't know whether the developers think that the overall behavior is
>> correct.
>
> The lack of + made me think that these files are not cheap copies,
> just
> regular, space-wasting copies, but clearly I was wrong about the
> meaning
> of it. So is it cheap or not? How do I tell the difference without
> the +
> sign?

I don't know if this copy will be cheap. But you can create a
throwaway repository and try it out.

If you find the copy is not cheap, and you don't want to use file-
level externals for this, then I recommend you do the other thing you
don't want to do, and commit the lib directory first, then create the
web* directories and copy things to them and commit them second. You
say it's a pain, but if this is a type of build you do often, I
expect you already have a script for it, so just change these steps
in the script.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2377529

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-31 21:38:55 CEST

This is an archived mail posted to the Subversion Users mailing list.