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

Re: Windows build severly broken due to read-only issues...

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-02-10 22:56:42 CET

Branko ─Œibej <brane@xbc.nu> writes:

> Jay, thanks for your analysis, it's extremely valuable!
> Which leads to a short sermon: In the past few weeks a lot of new
> stuff has gone into the code, mostly in the shape of fixes for
> bite-sized tasks. In hindsight, most of those changes were poorly
> thought out, at least as far as portability is concerned. Both
> copy-with-permissions and readonly admin files have managed to hose
> the Win32 build. While the file copy part is arguably an APR concern,
> the read-only file part is not. I think we have to be more careful
> about what goes in the code, otherwise we'll have a 1.0 that works on
> (some flavours of) Unix and nowhere else.
> Although I do try to keep up with the proposed patches, the sad fact
> is that one pair of eyes and a limited amount of time is simply not
> enough. That's why I find Jay's analysis of this particular problem so
> valuable. It's also a bit discouraging that people seem to overlook
> the broad picture so easily and think in terms of Unixy semantics
> instead. QED, that won't work for long.
> I do understand that thinking beyond "worksforme" makes it harder for
> many people to contribute, and I'm not criticising these contributions
> themselves. But I'm starting to see a trend here, and the closer we
> are to 1.0 in terms of functionality, the worse it'll get, unless we
> do something about it.

Expecting Unix developers to provide Win32 support just by thinking
about it is not going to work. We need input from Win32 developers.

Consider the read-only problem (which prompted the sermon) this was
first raised last year. Since then there has been no Win32 code
proposed to provide it. Not a single line. We had another discussion
last month, and the Win32 issue was raised again. I asked for a
possible Win32 interface (not an implementation, just an interface)
but nothing appeared. I asked for a description of the Win32
filesystem behaviour, still nothing. So in the absence of any other
input I proposed an interface, nobody said it was not suitable. In
fact, the comment I got was "this seems the way to go".

Now it is quite possible that the interface won't work on Win32. I
don't know, I'm not a Win32 developer. Perhaps the interface is OK and
it's the application code that needs to change, again it needs a Win32
person to point out the problems. Even better would be to provide a
patch, but describing the problem will do. If a problem is identified
I will try to fix it, but references to "sheer sloppy programming" do
not encourage me. The changes in question did not come out of the
blue, they were posted to the list precisely because I suspected that
there could be platform issues.

Within days of my starting to use apr_file_attrs_set an APR Win32
patch appears, so there are Win32 developers interested in Subversion.
I guess that Subversion currently has more developers using Unix than
Win32. I don't know how to encourage people with Win32 know-how to
contribute, but I wish they would. Until they do Win32 support is
inevitably going to be a second class citizen. I don't like that, I
want Win32 support (and OS X support, 64-bit support, etc.) However
it won't just happen, it requires appropriate developer interest.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:06 2006

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

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