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

Re: how to make svn _follow_ symbolic links?

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Tue, 21 Jul 2009 14:46:31 -0500

On Jul 21, 2009, at 07:38, Misha Aizatulin wrote:

> Ryan Schmidt wrote:
>
>> You do not need to create a separate repository to use externals.
>> Externals can reference items in the same repository.
>
> My situation is the following: I have a file (a bibliography list)
> that I would like to commit to two repositories. The repositories have
> restricted access, so I am the only person who has access to both of
> them. I can't easily get a third repository of my own, nor would I
> like
> to do it to store just a single file.
> Am I right in thinking, that externals cannot help in this case?

Ah. Then the only remaining options I see are to commit the file to
one repository and use an external from the other repository pointing
to it, or commit the file to both repositories and keep the two
versions in sync via a mechanism outside of Subversion (e.g. a script
you write).

>> When you say "from your hard drive", do you mean that the file is
>> unversioned, or is it in fact in a repository somewhere? If
>> unversioned then I can't suggest a solution, but as long as the file
>> is in a repository, then externals could be the answer.
>
> Yes, the files I want to reuse are not versioned in a public
> repository, nor do I see any reason for them to be.

Well if you don't want them to be versioned then Subversion has
nothing to do with them. I thought the point of the exercise was that
you did want the file to be in a repository (or, I'm now learning,
multiple repositories) but to keep changes in sync?

> Les Mikesell wrote:
>> But, why don't you include the 'real' copy in one of the
>> places you want it, and after committing it, reference the directory
>> holding it as an external in all those other places you want the same
>> things to appear?
>
> Partly because of access restriction mentioned above: people who
> have
> access to repository A might not have access to B and vice versa.
> Also, I wouldn't like the health of the repository A to depend on
> the
> health of B.

Ok, then scratch externals entirely. Commit the file to both
repositories and invent a way to keep them synchronized.

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

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

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.