Le 2025-02-16 21:03, Julien Puydt a écrit :
- the previous version used %%VERSION_NUM%% in only three places, the new one uses it more, so it broke my previous hack -- ;
As a matter of best practices, this should probably be defined in a single place and not "hardcoded" multiple times with templating.
- there are other things than the substitutions done by dune when compiling the package, which do not break the build, but will break some depending packages later on with strange and misleading errors.
Do you mean here that using the "official" tbz source tarballs for builds outside of a git tree will result in these errors? If so, that's a serious upstream build tool issue IMO.
As mentioned somewhere in the thread I proposed to dune upstream a simple mechanism to bypass this git reliance issue, which will make packaging much cleaner.
That's probably the way to go here. I would also suggest modifying dune-release so the git release tags end up with the substitutions already applied, to make it possible to simply export them and build them outside of a git tree.
Cheers, -- Julien Plissonneau Duquène
