Re: .dsp files in bundled apr(-util) (was: Subversion 0.21.0 released.)

On Wed, Apr 16, 2003 at 09:10:58PM +0200, Sander Striker wrote:
>...
> > The ASF maintains those files in CVS as text files (which they are, so it
> > makes a certain amount of sense). However, that means that they end up with
> > the newline style for whoever is packaging the code. If you get them from a
> > .tar.gz file, then (most likely) the packager was running on Unix and
> > they'll (incorrectly) have unix-style newlines.
> >
> > Normally, the ASF provides both .tar.gz files and .zip files. Where the .zip
> > is exactly the same source except for the newline style. We haven't been
> > doing the same thing for SVN, so the files are messed up for Windows users.
> >
> > I'm not sure what the best answer here is. There are quite a few options...
>
> I'd suggest converting the eol style to CRLF in release.sh.

Well, on my box that would be "unix2dos", but is that tool readily
available? Should we impose the requirement for its presence on the release
managers?

Oh! Hey... a teeny Python script would do the trick. We already know the
release manager has Python. Something like this:

#!/usr/bin/env python
# USAGE: unix2dos.py FILENAME
import sys
import string # avoid string methods to enable Python 1.5.2 usage
contents = open(sys.argv[1], 'rb').read()
open(sys.argv[1], 'wb').write(string.replace(contents, '\n', '\r\n'))

Hmm. I wonder if there are other things we can do with dist.sh given that we
know Python is present...

Cheers,
-g

-- 
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