I have a rather weird issue with github tarballs. In a version update of a coq platform project a folder vanished in the tar ball, although it is still there in git. Does someone have a good explanation for this?
See (https://github.com/coq-community/coq-dpdgraph/issues/95) for more details.
that's a manually created tarball, the automatic one at https://github.com/coq-community/coq-dpdgraph/archive/refs/tags/v1.0+8.15.tar.gz looks fine
Ah yes, thanks!
Yves chose to remove some things from the autoconf-created tarball ("manual")
I see. Well I will change the opam files to use the git hub tar ball. I find this rather confusing.
it's a consequence of using autoconf. I'd like to port to Dune instead, but the dpdgraph test suite is really tricky to port. Maybe I will ask Emilio for help during the hackathon in February
Btw.: I didn't really look at this in other opam files. Is it common practice to not use tar balls generated by a git server?
people have been doing this with autoconf for 20-30 years I think? dpdgraph is an old project...
this has nothing to do with autoconf, see commit
Michael was asking about the practice of generating tarballs via scripts (as opposed to from a Git tag)
Ok, thanks! I will watch out for this in the future and maybe ask people to change. As I said - I find it confusing if the tar ball doesn't match the git tag.
For the record, this is also the case when using Dune release for the many OCaml projects that use it (the GitHub tarball cannot be used because some substitution needs to happen in the tarball to correctly report the version number).
@Théo Zimmermann : thanks, interesting!
Last updated: Jun 05 2023 at 10:01 UTC