Scott Palmer wrote:
> On Jan 13, 2005, at 6:39 AM, Alex R. Mosteo wrote:
>
>> Hi,
>>
>> I have a project which uses an external (in another repository) folder
>> via the svn:externals property.
>>
>> Now if I make a copy of my project to a Tags folders to keep a
>> historical reference, is the revision of the external folder copied
>> too? In other words, I want to have a snapshot of my project and of
>> the external dependencies so, if I sometime later pull a copy of that
>> past tag, the external resource will be retrieved at its state at the
>> moment of the tag creation, not in its current revision.
>>
>> After summary inspection, I have the impression that the external
>> property only stores the path.
>
>
> It stores the URL to the repository.
>
> I'm not sure what happens currently when copying in this case, I haven't
> got to using svn:externals yet. But I can tell you what I think should
> happen.
>
> When you make the copy (tag), there should be an option that copies the
> svn:externals property and modifies it to add to the URL the current
> revision number of that URL (or the rev of the working copy in that
> folder as appropriate), if the URL doesn't already have a revision #.
Uh-oh I've just made a small test and I see that the svn:externals
aren't copied. Argh.
> I think svn:externals allows any URL, so svn:/blah/foo@123 should be
> valid. No, wait... checking the "book" I see an example that has:
>
> $ svn propget svn:externals calc
> third-party/sounds http://sounds.red-bean.com/repos
> third-party/skins http://skins.red-bean.com/repositories/skinproj
> third-party/skins/toolkit -r21 http://svn.red-bean.com/repos/skin-maker
>
> Note the -r21 on that last line, not the syntax I would have expected,
> and oddly it isn't discussed in that section of the book. It does imply
> that the revision can be specified though, so you could probably modify
> the svn:externals property yourself to include the revision. But an
> automated way to do this would certainly be helpful.
Indeed, the current situation seem bad enough for my intentions:
firstly, the external properties aren't copied (unless I've done
something wrong in my test, but it was simply a create - add external -
copy - verify missing external - verify external is in original folder).
Second, if I manually create the external in the copy I must take care
of adding the current revision of the resource.
> Someone who has actually done this should step up and clue us both in
> though :).
Yep, seems a bit strange you can't have multiple projects using a
external dependency (for example a library stored somewhere else) easily
synchronized. I suspect I'm missing the svn way for doing this.
Thanks Scott for your comments.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 14 11:55:24 2005