Given that he said lesson.exe I assume this is Windows and we do not
support symlinks.
With 1.6 we so support svn:externals for files though. So it could be
added just in one place and referenced in others.
With all the stuff we are doing around hashes and rep-sharing etc. It
is an interesting idea. What if the client told the server the
checksum of what it was sending and the server just said "don't bother
I already have one of those"?
Mark
On Wed, Mar 25, 2009 at 4:56 PM, Ben Collins-Sussman
<sussman_at_red-bean.com> wrote:
> Side note: have you considered using symlinks? Make file 1 "real",
> but then make all the other copies of it just unix symlinks to the
> original? (This would only work if you're sure that people never
> checkout tiny subtrees of the repository.)
>
> On Wed, Mar 25, 2009 at 3:40 PM, Phil Cross <pcross_at_pixeltecs.com> wrote:
>> I'm not sure where to post a suggestion for future versions but this is
>> definitely not a "bug". If this isn't the place or if you guys have already
>> thought of it, please let me know.
>>
>> I know that svn is typically used for source code control and not binary
>> files, so this may not be a common usage. I have a library of multimedia
>> that I maintain in version-control along side its source files. Sometimes I
>> have a situation where I have updated some multimedia "player" that is used
>> in several locations. Then, I updated all the directories where the player
>> resides with the newest player. Then I commit the revision. Subversion
>> proceeds to then upload the same file over and over again to the
>> repository. It seems that the client/server communication could be a little
>> smarter and only send a file once if it is the same file.
>>
>> As I am writing this, I am committing a media directory that contains 57
>> "lessons": media/lesson1, media/lesson2, etc... I have a 5MB file called
>> lesson.exe in each of these that I had to change. I have to keep the file
>> in each directory because my company often distributes a single "lesson" and
>> not the entire collection.
>>
>> I am not familiar with the protocol on the back end of subversion but I
>> assume it goes something like this:
>>
>> put file1 at /xyz
>> put file2 at /asdf
>> put file3 at /xyz/asdf
>>
>> Let's assume file1 and file3 are actually the same binary data. Maybe you
>> could just add some sort of back reference that the server could understand
>> like this:
>>
>> put file1 at /xyz label=A
>> put file2 at /asdf
>> put [A] at /xyz/asdf
>>
>> The client would have to be smart enough to determine which files match and
>> could inform the server in this manner. Obviously, this is only a suggested
>> implementation as I am not familiar with the protocol.
>>
>> Thanks (if nothing else, just for reading this),
>> Phil
>>
>>
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1420005
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1420062
Received on 2009-03-25 22:01:49 CET