Misha Aizatulin wrote:
>> But it can't be transparent. This would treat 'your' working copy
>> differently than you are asking it to treat everyone else's.
>>
>
> Isn't it what is happening with symlinks already?
No. If you commit your workspace, delete the whole thing, and check it
back out again on the same platform you will get a workspace that is the
same as what you committed.
> At the moment I can
> check in a representation of a symlink with svn:special property. If I
> check it out on Linux, it comes out as real symlink, but on Windows only
> the contents are recreated.
>
You don't get the contents of the target of the symlink. You get the
information you would need to be able to recreate the symlink on a
platform were symlinks have a meaning. The information you committed is
preserved there.
> Thus even with current svn there is no invariant saying that all
> working copies should be exactly the same.
>
Again, think about what should happen if you delete your own workspace
and ask svn to recreate it. With your symlink-replacing concept it will
still look more or less the same, but it won't work the same. You've
lost information that subversion is intended to maintain. And
philosophically, an update should give you the same thing as a a
checkout, so if you update your own existing working copy it should
convert your symlink into the copy it would deliver in a new checkout.
I don't think that's really what you want - and even if it is, it isn't
what a version control system should deliver.
--
Les Mikesell
lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2374626
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-23 01:54:09 CEST