summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorsternenseemann <sternenseemann@systemli.org>2025-09-15 15:07:26 +0200
committersternenseemann <sternenseemann@systemli.org>2025-09-26 11:56:55 +0200
commit1deb92346fcabee253bca127c316d2dabd1f8df1 (patch)
tree975d22973004723bf318e43a1e3fe3754d425faa /pkgs/development/python-modules/rangehttpserver
parent141143dab8dbcb09ef7bb90dc6ad406ca6209cc2 (diff)
haskellPackages.mkDerivation: enforce unix line endings in cabal files
Automatically use sed(1) to remove DOS line endings from .cabal files. This is intended to work around Hackage producing revised cabal files with DOS line endings (https://github.com/haskell/hackage-server/issues/316). This frequently leads to - patches failing to apply. Unfortunately there is no way to apply a patch with Unix line endings to a file with DOS line endings with GNU patch(1). Only the following combinations are supported: file patch comment Unix Unix DOS DOS using --binary DOS Unix Haven't tested it, but I assume it works because patch(1) converts the file to Unix line endings implicitly (which can be disabled using --binary), but never the patch… - Test suites sometimes involve the .cabal file which can be affected by the line endings. This behavior is enabled by default to prevent cases where (unrevised) packages regress when they get a revision later. Of course, the behavior is a little nonsensical for non-Hackage packages, but it is probably rarely an issue in practice. When DOS line endings need to be preserved, the user can pass `dontConvertCabalFileToUnix = true`. Supersedes #279248. Resolves #206840.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions