Le dimanche 16 février 2025 à 19:50 +0100, Julien Plissonneau Duquène a écrit : > Hi, > > Le 2025-02-16 17:00, Julien Puydt a écrit : > > > I have always considered the true way to know if you have the > > source of > > a package is: imagine you're stuck somewhere with a Debian mirror > > and > > no external link. Could you take over the development of the > > package at > > hand? > > Written like that it looks dramatic, but in that project there are > only > 5 occurences of %%VERSION_NUM%%. That's only 4 too many, and then it > would not be much different than many other project releases where a > script (not always provided), a bot (same) or plain old manual > intervention (not always fully documented) is used to adjust a > hardcoded > version number in some file somewhere at release time. But it's true > that if you're stranded somewhere you may have some free time at hand > to > implement your own layer of templating ^ ^.
You miss parts of the picture : - the previous version used %%VERSION_NUM%% in only three places, the new one uses it more, so it broke my previous hack -- ; - 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. My current hack creating a fake .git is in fact much more efficient and less fragile. 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. Cheers, J.Puydt
