You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Branko Čibej <br...@xbc.nu> on 2002/02/10 23:20:45 UTC
Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Philip Martin wrote:
>Branko Čibej <br...@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.
>
Pleas note that I did say I'm *not* criticising contributions (or
contributors). In fact, since I reviewed and o.k.'d your patch, part of
the blame for the current state of affairs is definitely mine.
As to sloppy programming ... sure, I should've put that differently.
Write it off to the bad mood of someone who has spent far too many
sleepless nights trying to get the dam' thing working on Win32, and
hasn't the good sense to calm down before posting. (Damn, it's past
midnight /again/.)
The problem, as usual, is not people but processes. In "doing something
about it" we shouldn't ask people who contribute patches to test on more
than one platform; we /should/, however try to make sure a change does
get tested on as broad a set of platforms as we can achieve. Note I said
"change", not "contribution". This will get more and more important the
closer we are to 1.0, because the cost of errors gets higher.
>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.
>
I'm afraid developer interest is not enough. Our goal for 1.0 is to have
a replacement for CVS. From my point of view that doesn't involve just
functionality; it means 1.0 has to run on at least the 10 most popular
platforms CVS runs on. It's not just Win32, I'm pretty sure we have
problems right now on popular Unixes, too.
In short: we have to define a set of target platforms for 1.0, and try
to find machines to test on. I can help with Win32, HP-UX and Solaris,
maybe AIX with a bit of luck.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python's urlparse.urljoin() (was: Re: Subversion
portability)
Posted by Bruce Atherton <br...@callenish.com>.
At 12:35 PM 2/12/2002 -0800, Greg Stein wrote:
>If anybody can come up with a patch for urlparse.py, then I can check it
>into Python itself :-)
At first, I thought the problem was that the file scheme is in the list of
schemes that use the network host name part of a URL, but a file URL does
no such thing. Or does it? Can an NFS server or netware server to be
specified as file://nfs.mydomain.com/path/to/file.txt, for example?
Apparently it can:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Lib/urlparse.py?rev=1.18&content-type=text/vnd.viewcvs-markup
So if this is correct, the real change belongs in urlunsplit(). I believe
this patch is correct:
Log:
* urlparse (urlunsplit): Correct test for prepending a "//" to a URL. This
fixes file URLs so that they unparse as "file:///path/to/file" rather than
"file:/path/to/file".
Index: urlparse.py
===================================================================
RCS file: /cvsroot/python/python/dist/src/Lib/urlparse.py,v
retrieving revision 1.31
diff -u -r1.31 urlparse.py
--- urlparse.py 16 Nov 2001 02:52:57 -0000 1.31
+++ urlparse.py 12 Feb 2002 21:54:04 -0000
@@ -126,7 +126,7 @@
return urlunsplit((scheme, netloc, url, query, fragment))
def urlunsplit((scheme, netloc, url, query, fragment)):
- if netloc or (scheme in uses_netloc and url[:2] == '//'):
+ if netloc or (scheme in uses_netloc and url[:2] != '//'):
if url and url[:1] != '/': url = '/' + url
url = '//' + (netloc or '') + url
if scheme:
file:/// URLs using Python's urlparse.urljoin() (was
Subversion portability)
Posted by Bruce Atherton <br...@callenish.com>.
At 02:29 PM 8/5/2002 -0500, Karl Fogel wrote:
>Is your workaround below still applicable, or did we solve this some
>other way? I didn't see anything in the logs indicating that this had
>been applied, nor that the problem had been addressed...
This wasn't a patch to a specific file, it was a hack to add whenever
someone wanted to use the Python urlparse.urljoin() method and still keep
the proper file:/// format. Grepping through the Subversion codebase now I
don't see urljoin() being used anywhere, probably at least in part because
of the slash-stripping bug.
I guess the hack is still applicable for anyone that wants to write a
python test that uses urlparse.urljoin() with file:/// URLs in a portable
way. I don't think there is anything specific that needs to be done about
it, though. I've changed the subject to make it easier to find in case
anyone needs it.
Thanks for reminding me about this. It prompted me to send in the patch to
fix the underlying Python bug.
[hack follows]
> # FIXME: On at least some versions of Python, a bug in urlparse.urljoin()
> # strips required slashes out of a "file:" URL. This repairs the damage.
> # Once Python is fixed to get it right, the required Python version
> # should be upped and this code should be stripped.
> import re
>
> find_bad_url = re.compile("file:/[^/]")
> if (find_bad_url.match(urlstring)) is not None:
> urlstring = urlstring[0:5] + "//" + urlstring[5:]
Re: Subversion portability
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Bruce, I'm reviewing some pending patches -- some of the older ones
may be obsolete by now, either because already applied, or because
some other fix did the job.
Is your workaround below still applicable, or did we solve this some
other way? I didn't see anything in the logs indicating that this had
been applied, nor that the problem had been addressed...
-Karl
Bruce Atherton <br...@callenish.com> writes:
> >Greg Stein suggested urlparse.urljoin
> >
> >http://subversion.tigris.org/servlets/ReadMsg?msgId=53677&listName=dev
> >
> >but it didn't work for me
> >
> >http://subversion.tigris.org/servlets/ReadMsg?msgId=53693&listName=dev
> >
> >since file:///xxx gets converted to file:/xxx
>
> Same for me on Windows using Activestate Python 2.1.1.
>
> This should be easy to work around, though, if in a grotesque way:
>
> # FIXME: On at least some versions of Python, a bug in urlparse.urljoin()
> # strips required slashes out of a "file:" URL. This repairs the damage.
> # Once Python is fixed to get it right, the required Python version
> # should be upped and this code should be stripped.
> import re
>
> find_bad_url = re.compile("file:/[^/]")
> if (find_bad_url.match(urlstring)) is not None:
> urlstring = urlstring[0:5] + "//" + urlstring[5:]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Python's urlparse.urljoin() (was: Re: Subversion portability)
Posted by Greg Stein <gs...@lyra.org>.
If anybody can come up with a patch for urlparse.py, then I can check it
into Python itself :-)
(of course, given that Python 2.2 was just released, I don't expect 2.3 to
come out for a long while...)
Cheers,
-g
On Tue, Feb 12, 2002 at 12:16:57PM -0800, Bruce Atherton wrote:
> At 06:44 PM 2/11/2002 +0000, Philip Martin wrote:
>...
> >Greg Stein suggested urlparse.urljoin
> >
> >http://subversion.tigris.org/servlets/ReadMsg?msgId=53677&listName=dev
> >
> >but it didn't work for me
> >
> >http://subversion.tigris.org/servlets/ReadMsg?msgId=53693&listName=dev
> >
> >since file:///xxx gets converted to file:/xxx
>
> Same for me on Windows using Activestate Python 2.1.1.
>
> This should be easy to work around, though, if in a grotesque way:
>
> # FIXME: On at least some versions of Python, a bug in urlparse.urljoin()
> # strips required slashes out of a "file:" URL. This repairs the damage.
> # Once Python is fixed to get it right, the required Python version
> # should be upped and this code should be stripped.
> import re
>
> find_bad_url = re.compile("file:/[^/]")
> if (find_bad_url.match(urlstring)) is not None:
> urlstring = urlstring[0:5] + "//" + urlstring[5:]
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability
Posted by Bruce Atherton <br...@callenish.com>.
At 06:44 PM 2/11/2002 +0000, Philip Martin wrote:
>Ben Collins-Sussman <su...@collab.net> writes:
>
> > Branko Äibej <br...@xbc.nu> writes:
> >
> > > os.path.join() on windows never gives you a valid URL. *bonk*!
> >
>
>Greg Stein suggested urlparse.urljoin
>
>http://subversion.tigris.org/servlets/ReadMsg?msgId=53677&listName=dev
>
>but it didn't work for me
>
>http://subversion.tigris.org/servlets/ReadMsg?msgId=53693&listName=dev
>
>since file:///xxx gets converted to file:/xxx
Same for me on Windows using Activestate Python 2.1.1.
This should be easy to work around, though, if in a grotesque way:
# FIXME: On at least some versions of Python, a bug in urlparse.urljoin()
# strips required slashes out of a "file:" URL. This repairs the damage.
# Once Python is fixed to get it right, the required Python version
# should be upped and this code should be stripped.
import re
find_bad_url = re.compile("file:/[^/]")
if (find_bad_url.match(urlstring)) is not None:
urlstring = urlstring[0:5] + "//" + urlstring[5:]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Philip Martin <ph...@codematters.co.uk>.
Ben Collins-Sussman <su...@collab.net> writes:
> Branko Äibej <br...@xbc.nu> writes:
>
> > os.path.join() on windows never gives you a valid URL. *bonk*!
>
> Oy, yeesh.
>
> Well then this sounds like a handful of trivial fixes, then. :-)
Greg Stein suggested urlparse.urljoin
http://subversion.tigris.org/servlets/ReadMsg?msgId=53677&listName=dev
but it didn't work for me
http://subversion.tigris.org/servlets/ReadMsg?msgId=53693&listName=dev
since file:///xxx gets converted to file:/xxx
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Ben Collins-Sussman <su...@collab.net>.
Branko Čibej <br...@xbc.nu> writes:
> os.path.join() on windows never gives you a valid URL. *bonk*!
Oy, yeesh.
Well then this sounds like a handful of trivial fixes, then. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Branko Čibej <br...@xbc.nu>.
Karl Fogel wrote:
>Ben Collins-Sussman <su...@collab.net> writes:
>
>>We gotta fix that. There's *no* reason for this. We're using
>>'os.path.join()' everywhere in an attempt to be portable. If we're
>>being un-portable in some other way, that's a bug.
>>
>
>Yeah! Hmm, why don't they run in Windows?
>
os.path.join() on windows never gives you a valid URL. *bonk*!
>(In the meantime, though, an automated build/check system can just run
>some of the tests by hand, and ignore others, until they work on
>Windows too.)
>
Sure.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Ben Collins-Sussman <su...@collab.net> writes:
> We gotta fix that. There's *no* reason for this. We're using
> 'os.path.join()' everywhere in an attempt to be portable. If we're
> being un-portable in some other way, that's a bug.
Yeah! Hmm, why don't they run in Windows?
(In the meantime, though, an automated build/check system can just run
some of the tests by hand, and ignore others, until they work on
Windows too.)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Ben Collins-Sussman <su...@collab.net>.
Branko Čibej <br...@xbc.nu> writes:
> The biggest problem is that the Pyhon tests don't work on Windows
> right now. The rest is no problem -- build can be automated, so can
> mailoff, and I can (and do) use cygwin to run the shell scripts.
We gotta fix that. There's *no* reason for this. We're using
'os.path.join()' everywhere in an attempt to be portable. If we're
being un-portable in some other way, that's a bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Branko Čibej <br...@xbc.nu>.
Karl Fogel wrote:
>I wrote:
>
>>But I'd like to second Philip's comments: the issue here isn't that
>>the changes aren't well thought-out, it's that people are expecting
>>...
>>
>
>Sigh, and once again it turns out there was no need to write it,
>because Branko beat me to it in a separate thread... Sorry 'bout that.
>I did read all of the orginal thread first, at least. :-)
>
>>In short: we have to define a set of target platforms for 1.0, and try
>>to find machines to test on. I can help with Win32, HP-UX and Solaris,
>>maybe AIX with a bit of luck.
>>
>
>Branko, are you doing automated "make; make check" on these platforms?
>Do you want to be?
>
I'm not doing it, but I plan to grab some space on those machines and
set it up.
>I've been thinking it's time to set up an automated build/test system,
>that would mail nightly results to a new list
>
> svn-breakage@subversion.tigris.org
>
>or something. The most important of the automated platforms would be
>Windows, because it's what we break most often. How hard would it be
>to set up automated build and mailoff on Windows?
>
The biggest problem is that the Pyhon tests don't work on Windows right
now. The rest is no problem -- build can be automated, so can mailoff,
and I can (and do) use cygwin to run the shell scripts.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: new mailing list (was: Subversion portability)
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Greg Stein <gs...@lyra.org> writes:
> Reposting with a clearer subject line, so that existing subscribers might
> actually realize a new (potentially interesting) mailing list has been
> created.
Thanks! (d'oh)
> I also believe that Karl is intending that people who are setting up
> auto-builds will send the results to this list. IOW, the activity on the
> list isn't necessarily going to be non-zero until people start posting.
Yes, please, that's the idea. :-)
> (I think it would also be good to moderate the list, and only accept reports
> from auto-build systems; keep discussion on dev@)
Good idea. I've set it to moderated, with gstein and myself as the
only moderators (other volunteers welcome for this), and as we get
mails, we can add them to the allowed-posters list.
-K
> On Mon, Feb 11, 2002 at 08:20:02PM -0600, Karl Fogel wrote:
> > David Summers <da...@summersoft.fay.ar.us> writes:
> > > I've already got an automated compile set up for Redhat Linux 7.2. I
> > > could forward that to the appropriate mailing list if/when it is set up.
> >
> > Great! After careful consideration, I've gone for the whimsical name
> >
> > svn-breakage@svn.collab.net
> >
> > The list is created now, I'm the only subscriber so far. Anyone who
> > wants to receive automated build/check emails please subscribe.
> >
> > The list's description says:
> >
> > This list receives automated messages from automated build and test
> > systems. For example, if you have set up an automated nightly
> > "make; make check" system to test Subversion on a particular
> > platform, the system can send its output to this list. Suggested
> > format for subject lines of such mail messages:
> >
> > svn rev N: PASS (FreeBSD ...)
> >
> > where N is a revision number, and the information in parens is a
> > platform string, see the PLATFORMS file for more examples.
> > Substitute FAIL for PASS if the test fails. (Also, please set the
> > Reply-to header on such mails to dev@subversion.tigris.org, so any
> > problems are followed up on the main list.)
> >
> >
> > -Karl
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
>
> --
> Greg Stein, http://www.lyra.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
new mailing list (was: Subversion portability)
Posted by Greg Stein <gs...@lyra.org>.
Reposting with a clearer subject line, so that existing subscribers might
actually realize a new (potentially interesting) mailing list has been
created.
I also believe that Karl is intending that people who are setting up
auto-builds will send the results to this list. IOW, the activity on the
list isn't necessarily going to be non-zero until people start posting.
(I think it would also be good to moderate the list, and only accept reports
from auto-build systems; keep discussion on dev@)
Cheers,
-g
On Mon, Feb 11, 2002 at 08:20:02PM -0600, Karl Fogel wrote:
> David Summers <da...@summersoft.fay.ar.us> writes:
> > I've already got an automated compile set up for Redhat Linux 7.2. I
> > could forward that to the appropriate mailing list if/when it is set up.
>
> Great! After careful consideration, I've gone for the whimsical name
>
> svn-breakage@svn.collab.net
>
> The list is created now, I'm the only subscriber so far. Anyone who
> wants to receive automated build/check emails please subscribe.
>
> The list's description says:
>
> This list receives automated messages from automated build and test
> systems. For example, if you have set up an automated nightly
> "make; make check" system to test Subversion on a particular
> platform, the system can send its output to this list. Suggested
> format for subject lines of such mail messages:
>
> svn rev N: PASS (FreeBSD ...)
>
> where N is a revision number, and the information in parens is a
> platform string, see the PLATFORMS file for more examples.
> Substitute FAIL for PASS if the test fails. (Also, please set the
> Reply-to header on such mails to dev@subversion.tigris.org, so any
> problems are followed up on the main list.)
>
>
> -Karl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
David Summers <da...@summersoft.fay.ar.us> writes:
> OK, next question...how do you subscribe to this list? I tried
> svn-breakage-subscribe@svn.collab.net and svn-breakage-help@svn.collab.net
> and both returned "Unknown User".....Or was that supposed to be
> @subversion.tigris.org?
@subversion.tigris.or; see
http://subversion.tigris.org/servlets/ProjectMailingListList
for details.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken
due to read-only issues...]
Posted by David Summers <da...@summersoft.fay.ar.us>.
OK, next question...how do you subscribe to this list? I tried
svn-breakage-subscribe@svn.collab.net and svn-breakage-help@svn.collab.net
and both returned "Unknown User".....Or was that supposed to be
@subversion.tigris.org?
Thanks,
- David
On 11 Feb 2002, Karl Fogel wrote:
> Great! After careful consideration, I've gone for the whimsical name
>
> svn-breakage@svn.collab.net
>
> The list is created now, I'm the only subscriber so far. Anyone who
> wants to receive automated build/check emails please subscribe.
>
> The list's description says:
>
> This list receives automated messages from automated build and test
> systems. For example, if you have set up an automated nightly
> "make; make check" system to test Subversion on a particular
> platform, the system can send its output to this list. Suggested
> format for subject lines of such mail messages:
>
> svn rev N: PASS (FreeBSD ...)
>
> where N is a revision number, and the information in parens is a
> platform string, see the PLATFORMS file for more examples.
> Substitute FAIL for PASS if the test fails. (Also, please set the
> Reply-to header on such mails to dev@subversion.tigris.org, so any
> problems are followed up on the main list.)
>
>
> -Karl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
--
David Wayne Summers "Linux: Because reboots are for upgrades!"
david@summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
David Summers <da...@summersoft.fay.ar.us> writes:
> I've already got an automated compile set up for Redhat Linux 7.2. I
> could forward that to the appropriate mailing list if/when it is set up.
Great! After careful consideration, I've gone for the whimsical name
svn-breakage@svn.collab.net
The list is created now, I'm the only subscriber so far. Anyone who
wants to receive automated build/check emails please subscribe.
The list's description says:
This list receives automated messages from automated build and test
systems. For example, if you have set up an automated nightly
"make; make check" system to test Subversion on a particular
platform, the system can send its output to this list. Suggested
format for subject lines of such mail messages:
svn rev N: PASS (FreeBSD ...)
where N is a revision number, and the information in parens is a
platform string, see the PLATFORMS file for more examples.
Substitute FAIL for PASS if the test fails. (Also, please set the
Reply-to header on such mails to dev@subversion.tigris.org, so any
problems are followed up on the main list.)
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken
due to read-only issues...]
Posted by David Summers <da...@summersoft.fay.ar.us>.
I've already got an automated compile set up for Redhat Linux 7.2. I
could forward that to the appropriate mailing list if/when it is set up.
- David
On 11 Feb 2002, Karl Fogel wrote:
> I wrote:
> > But I'd like to second Philip's comments: the issue here isn't that
> > the changes aren't well thought-out, it's that people are expecting
> > ...
>
> Sigh, and once again it turns out there was no need to write it,
> because Branko beat me to it in a separate thread... Sorry 'bout that.
> I did read all of the orginal thread first, at least. :-)
>
> > In short: we have to define a set of target platforms for 1.0, and try
> > to find machines to test on. I can help with Win32, HP-UX and Solaris,
> > maybe AIX with a bit of luck.
>
> Branko, are you doing automated "make; make check" on these platforms?
> Do you want to be?
>
> I've been thinking it's time to set up an automated build/test system,
> that would mail nightly results to a new list
>
> svn-breakage@subversion.tigris.org
>
> or something. The most important of the automated platforms would be
> Windows, because it's what we break most often. How hard would it be
> to set up automated build and mailoff on Windows?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
--
David Wayne Summers "Linux: Because reboots are for upgrades!"
david@summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
I wrote:
> But I'd like to second Philip's comments: the issue here isn't that
> the changes aren't well thought-out, it's that people are expecting
> ...
Sigh, and once again it turns out there was no need to write it,
because Branko beat me to it in a separate thread... Sorry 'bout that.
I did read all of the orginal thread first, at least. :-)
> In short: we have to define a set of target platforms for 1.0, and try
> to find machines to test on. I can help with Win32, HP-UX and Solaris,
> maybe AIX with a bit of luck.
Branko, are you doing automated "make; make check" on these platforms?
Do you want to be?
I've been thinking it's time to set up an automated build/test system,
that would mail nightly results to a new list
svn-breakage@subversion.tigris.org
or something. The most important of the automated platforms would be
Windows, because it's what we break most often. How hard would it be
to set up automated build and mailoff on Windows?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by cm...@collab.net.
Branko =?UTF-8?B?xIxpYmVq?= <br...@xbc.nu> writes:
> >Now, I seem to recall a rumor that Subversion builds pretty much
> >out-of-the-box on Win32 these days. If this is true, then the Win32
> >platform will regain some of my attention.
>
> It does now, except for Berkeley DB, which you really don't want to
> rebuild every time. There's a binary BDB package on the downloads
> page.
Yep, saw it. I just successfully built Subversion on Windows.
> (There was also a binary neon package there, until I fixed the neon
> build. Did you ever look there? :-)
Yeah, I remember using that once before, now. I must have forgotten
about it, though.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Branko Čibej <br...@xbc.nu>.
cmpilato@collab.net wrote:
>Branko =?UTF-8?B?xIxpYmVq?= <br...@xbc.nu> writes:
>
>>The problem, as usual, is not people but processes. In "doing something
>>about it" we shouldn't ask people who contribute patches to test on more
>>than one platform; we /should/, however try to make sure a change does
>>get tested on as broad a set of platforms as we can achieve. Note I said
>>"change", not "contribution". This will get more and more important the
>>closer we are to 1.0, because the cost of errors gets higher.
>>
>
>I'm willing to assist in this area as much as possible. I do have a
>Win32 box sitting next to me at the office whose job is, technically
>speaking, to provide me a mechanism by which to keep Subversion on the
>right track in The Win-world. My failure to do so thus far (well, at
>least in some time now) is laziness on my part to fight with the build
>situation. Until recently, Neon's Windows build was sooooooo broken,
>and I tired of re-implementing custom Neon build stuffs every time we
>xupgrade to a new version.
>
>Now, I seem to recall a rumor that Subversion builds pretty much
>out-of-the-box on Win32 these days. If this is true, then the Win32
>platform will regain some of my attention.
>
It does now, except for Berkeley DB, which you really don't want to
rebuild every time. There's a binary BDB package on the downloads page.
(There was also a binary neon package there, until I fixed the neon
build. Did you ever look there? :-)
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by cm...@collab.net.
Branko =?UTF-8?B?xIxpYmVq?= <br...@xbc.nu> writes:
> The problem, as usual, is not people but processes. In "doing something
> about it" we shouldn't ask people who contribute patches to test on more
> than one platform; we /should/, however try to make sure a change does
> get tested on as broad a set of platforms as we can achieve. Note I said
> "change", not "contribution". This will get more and more important the
> closer we are to 1.0, because the cost of errors gets higher.
I'm willing to assist in this area as much as possible. I do have a
Win32 box sitting next to me at the office whose job is, technically
speaking, to provide me a mechanism by which to keep Subversion on the
right track in The Win-world. My failure to do so thus far (well, at
least in some time now) is laziness on my part to fight with the build
situation. Until recently, Neon's Windows build was sooooooo broken,
and I tired of re-implementing custom Neon build stuffs every time we
xupgrade to a new version.
Now, I seem to recall a rumor that Subversion builds pretty much
out-of-the-box on Win32 these days. If this is true, then the Win32
platform will regain some of my attention.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Subversion portability [Was: Re: Windows build severly broken due to read-only issues...]
Posted by Philip Martin <ph...@codematters.co.uk>.
Branko Äibej <br...@xbc.nu> writes:
> As to sloppy programming ... sure, I should've put that
> differently. Write it off to the bad mood of someone who has spent far
> too many sleepless nights trying to get the dam' thing working on
> Win32, and hasn't the good sense to calm down before posting. (Damn,
> it's past midnight /again/.)
OK, perhaps I was being over sensitive. Anyone who posts/commits code
should expect to get comments.
Philip, who notes it's 2am here
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org