On Jul 21, 2009, at 15:04, Misha Aizatulin wrote:
>>>> 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 guess I wasn't clear: I don't want them versioned separately,
> but of
> course I want to commit them to the two repositories I have mentioned.
> The problem is that I cannot and I don't want to point from one
> repository to the other.
>> Ok, then scratch externals entirely. Commit the file to both
>> repositories and invent a way to keep them synchronized.
> But hasn't this way been invented a long time ago? I think this is
> exactly what symbolic links are for! The only obstacle is that svn
> chokes on symbolic links and that's why I am discussing it here.
> Is there any reason not to implement following symbolic links? Is
> it a
> design decision or just due to the fact that no one requested it so
> Again, shall I write a feature request?
So what is the workflow you desire? It sounds to me like you want the
Check out working copy A from some place in repository A.
Check out working copy B from some place in repository B.
Both working copies contain a file bib which you would like to be
identical in both repositories.
Delete file bib in both working copies and replace them with a
symlink to a file bib which is somewhere on your hard drive outside
of a working copy.
Make a change to bib.
Go into working copy A and commit.
Go into working copy B and commit.
Thus sending your changes into both repository A and B.
Anybody else who checks out a working copy from repository A or B
will get the bib file and will know nothing of your symlink situation
on your local machine.
Is that accurate?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-21 22:28:00 CEST