Follow-up Comment #8, patch #2829 (project freeciv):
> That does mean that the typical developer experience (running
> from source directory) diverges further from the "mission mode"
> (install and run), perhaps increasing the possibility of
> install-only bugs not spotted until too late.
If the only problem we're solving is line endings on Windows, can we apply
that transformation even later, as part of the Windows installer building
process.
IIRC zip/unzip can convert line endings, although I don't know if it uses a
possibly-unsafe heuristic. Maybe if we start the Windows build process with a
suitable 'unzip' invocation from the zipped source release (which we'd have
carefully created with appropriate files marked as text if necessary)?
> The arguments change if we're doing more stuff as part of
> "building" text files, such as automatic substitutions.
One such that I've considered is automatically copying the ruleset help from
the classic ruleset to other rulesets (which would have comments like ";
@UNITTYPEHELP@" in the source), so we only have to maintain the text in one
place. That might be worth the risk of having a separate "make install" step
for data (plus since it's only comments, using the datafiles in the source
tree would actually be fine).
_______________________________________________________
Reply to this item at:
<http://gna.org/patch/?2829>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Freeciv-dev mailing list
[email protected]
https://mail.gna.org/listinfo/freeciv-dev
