Re: [PMX:SPAM8%] RE: RE: Re: Visual Studio.Net and Subversion - Will this make it into a release?

Demyanovich, Craig - Apogent wrote:
>>I think the problem people have with this is that you can't
>>pick up the wc and move it somewhere else without having a
>>modified svn program on that system. For example, you can't
>>move a Windows wc to Linux.

For all users asking why this use case was developed, you should be aware that
more than a few people develop cross platform apps using a /shared/ WC (like
through a Samba share). Some significant effort has gone into enabling this
ability, which is why the common .svn directory value is so important.

To paraphrase the discussion that I have witnessed (I'm not a voice of authority
here):

1) The "bug" is in VS.NET via IIS, which cannot handle directory names with only
extensions;

2) The next version of VS.NET won't work that way;

3) The universe of VS.NET users who develop web apps _and_ might use Subversion
is small (compared to other userbases);

4) There are plenty of workarounds available for a site-specific fix.

Therefore, nothing need be done in Subversion itself. That said, if someone
came up with an especially good patch which fixed the "bug" without causing more
problems for others, it would likely be seriously considered. There are other,
much more useful enhancements that need to be made (locking, etc) to spend much
time with this misfeature on the part of M$loth...

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org