Open peti opened 5 years ago
This might be the first tarball I created using cabal new-sdist
instead of cabal sdist
.
The timestamps are probably a reproducibility feature — as https://www.haskell.org/cabal/users-guide/nix-local-build.html#cabal-new-sdist states:
These archives are stable and two archives of the same format built from the same source will hash to the same value.
I don't know why the text files are made executable though. They certainly aren't in my source directory.
I opened https://github.com/haskell/cabal/issues/5813 about this issue. Let's see what the cabal gurus think about this.
BTW I was trying to reproduce this for other projects and so far from my limited testing this happens only(?) with Extra-Source-Files
but not Extra-Doc-Files
.
I forget when exactly the latter was introduced but I think it was well before Cabal-2 anyway...
and I reckon all the Glob Extra-Source-Files
are actually Extra-Doc-Files
. :)
Apparently extra-doc-files was introduced in 1.20 — according to the changelog at https://github.com/haskell/cabal/blob/master/Cabal/ChangeLog.md#12000-johan-tibell-april-2014 at least, although the docs at https://www.haskell.org/cabal/users-guide/developing-packages.html#pkg-field-extra-doc-files say it's in since 1.18.
This seems to have grown organically in Glob.cabal
anyway, since originally only the tests were added as extras and the other documentation came only later. My bad for not realizing the more suitable field at the time, I guess.
I noticed the following issues with the latest Hackage release tarball:
Is that intentional?