diff options
| author | sternenseemann <sternenseemann@systemli.org> | 2025-09-21 16:59:24 +0200 |
|---|---|---|
| committer | sternenseemann <sternenseemann@systemli.org> | 2025-09-22 13:24:02 +0200 |
| commit | ce72c7443285ce5774e59471ade81d5ac47503a8 (patch) | |
| tree | 8a64cbf85923415f5f33d4f135b829c94060e8d8 /pkgs/development/python-modules/rangehttpserver | |
| parent | 9dd4e71f8e09034e0949b818ef4676a36db2f394 (diff) | |
haskell.compiler: remove references xattr missing flag issues
darwin.xattr used to be a fork of python3.pkgs.xattr.
bafc6ff88df03e765a35efd140e switched darwin.xattr to Apple's new
C implementation of the tool.
When I originally packaged darwin.xattr (283d622397539f196416657d),
I linked tickets on the original tool's issue tracker suggesting to
add support for flags added by Apple in their fork. This has since
happened, so we could possibly switch to python3.pkgs.xattr.
However, I think it's no longer a good idea:
- Bootstrapping-wise a C tool is considerably simpler.
- GHC upstream tests against Apple's xattr(1) implementation in their
CI. Especially now, since they no longer share a direct ancestry,
it seems unwise to assume the tools will behave the same.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions