(moved to dev@ because it looks to me like there should be more
prominent notice that .zip files are for Windows only)
On Apr 17, 2005, at 1:46 AM, Ryan Saunders wrote:
> I built it from the zip.
> Even so, are the DOS end-of-lines really necessary/beneficial in this
> shell script? Aren't even the Win32 ports of bash and sh capable of
> UNIX EOLs? If so, I can't see a good reason not to keep all the shell
> in UNIX format. This is the only build error I encountered -- meaning
> that if
> this were fixed then the zip archive would work fine, both on UNIX AND
> On Saturday 16 April 2005 15:42, you wrote:
>> On Apr 16, 2005, at 1:42 PM, Ryan Saunders wrote:
>>> The cause of the problem is that install-sh has DOS-style
>>> linebreaks, which evidently breaks the #! shebang handling ...
>> Building from tarball (.tar.gz or .tar.bz2) or zip? zip is only for
>> Windows builds. All Unix-like OSes need to use the one of the
>> or I would expect they would encounter just what you describe.
Please keep replies to the Subversion mailing list(s). I don't know
about your followup questions. I just happened to correctly guess the
source of your trouble from reading the Subversion mailing lists and
also having some experience seeing CRLF line endings cause Unix shell
scripts not function.
I don't see it clearly indicated that zip is intended for Windows
systems only and that all other systems are expected to use the tar.gz
or tar.bz2 files (which are identical tar archives with different
compression only). Maybe you can double-check that there is no notice?
That seems the area that is most readily fixed.
> Aren't even the Win32 ports of bash and sh capable of handling UNIX
> EOLs? ... -- meaning that if this were fixed then the zip archive
> would work fine, both on UNIX AND win-32.
I've no idea about Win32 ports of anything. I avoid Windows like the
plague myself. :-) But I do want to mention that this type of thinking
recently showed up on the dev@ list (and some of it might have been
cross-posted to users@ too). It appears to be unwise to assume
anything about building Subversion on different platforms if you don't
actually build Subversion on the platforms you're speaking about
(though Unix-to-Unix system knowledge is often transferable, though not
always, especially in the area of shared libraries).
Devs, I've attached a proposed website patch below because this
confusion has happened a couple times before, for example:
I didn't see any notice similar to what I propose when I went hunting
for one just now.
Add notice where pages link to
that users know that the *.zip files are for Windows and that other
should use the *.tar.gz or *.tar.bz2 files.
* www/project_packages.html: Add notice about which archives a user
download for Windows vs other systems where the user sees the link
to the download area.
* www/getting_subversion.html: Ditto.
--- project_packages.html (revision 14270)
+++ project_packages.html (working copy)
@@ -94,7 +94,9 @@
<p>The latest source release can be found <a
in this directory</a>, in the file-sharing area of the Subversion
-website. Be sure to read the <a
+website. (Windows users should download the <tt>*.zip</tt> and all
+other users should download the <tt>*.tar.gz</tt> or
+Be sure to read the <a
href="getting_subversion.html">general instructions</a> for building
from the source tarball, and the <a
--- getting_subversion.html (revision 14270)
+++ getting_subversion.html (working copy)
@@ -23,7 +23,9 @@
<li><p>Download the latest tarball distribution from the <a
folderID=260">Source Releases Area</a>.</p></li>
folderID=260">Source Releases Area</a>.
+ (Windows users should download the <tt>*.zip</tt> and all other
+ should download the <tt>*.tar.gz</tt> or
<li><p>Build and install it according to the instructions in the
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Apr 17 18:54:03 2005