Thanks Bill and Mladen. It makes sense to check for wrong svn metadata,
although the problem at the moment is, that unix distributions are build
on the windows platform.
So even with correct settings those files have Windows line endings
without correcting. Bill Wrowes comments are interesting, because it
might be easier to do two passes through the same build procedure with
different export flags. Combined with your script, we then wouldn't need
to manage fragile file lists.
Since I never did a TC release, I think it's time for Mark, Filip or
Remy to comment, what they prefer.
Regards,
Rainer
Mladen Turk wrote:
William A. Rowe, Jr. wrote:
Rainer Jung wrote:
- cleanup and prepare for each of the targets underneath or "release".
Either way, since in the source tgz target there is already an
exclude list, I would prefer to update that exclude list and use the
same one whereever possible, so something like:
FYI - this is all overkill. If you are packaging on win32, svn export
does your cr/lf line endings by default, but you can create a unix
package with svn export --native-eol LF. Contrawise on unix, you can
create the win32 .zip with svn export --native-eol CRLF.
I did set svn properties for all non-binary files to
have eol-style native. However it seems that lots of files
have been added since the last update, and commiters didn't
follow the suggestion for svn config file [auto-props]
I posted few years back :)
Here are two windows scripts that will setup the correct props
for all files in the repo.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
