elpi -version prints... %%VERSION_NUM%% !
SnarkBoojum opened this issue · comments
It should definitely answer a correct version!
Hum, this is "normal", it is part of the dune workflow
gares@ollypat:~/LPCIC/elpi$ dune exec -- elpi -version
%%VERSION_NUM%%
gares@ollypat:~/LPCIC/elpi$ dune subst
gares@ollypat:~/LPCIC/elpi$ dune exec -- elpi -version
ppx src/compiler.pp.ml
ocamldep src/.elpi.objs/compiler.pp.ml.d
ocamlopt src/.elpi.objs/native/elpi__Compiler.{cmx,o}
ocamlopt src/elpi.{a,cmxa}
ocamlc .elpi_REPL.eobjs/byte/dune__exe__Elpi_REPL.{cmi,cmo,cmt}
ocamlopt .elpi_REPL.eobjs/native/dune__exe__Elpi_REPL.{cmx,o}
ocamlopt elpi_REPL.exe
1.13.7-35-g9b71426
Released tarballs do contain a version number. If you build from git you need to run dune subst to get it
There's more to say about it:
jpuydt@phaeris:~/Debian/build/elpi-1.13.7$ dune exec -- elpi -version
%%VERSION_NUM%%
jpuydt@phaeris:~/Debian/build/elpi-1.13.7$ dune subst
jpuydt@phaeris:~/Debian/build/elpi-1.13.7$ dune exec -- elpi -version
%%VERSION_NUM%%
even a "dune build" right in doesn't help. I'm using a github tarball, if that helps.
Where is the version supposed to come from for "dune subst" to work? It's only in README.md as far as I can tell...
I got around it for the Debian package.
you are not using the .tbz, that one has the version
Well, I'm using a github-provided tarball, so I'll let my workaround in place: it works nicely.
Also, looking at this bug report, it looks like some people would like to know you're alive and kicking.
I retired from debian, this means I don't work in that project anymore, not that I'm in a coma or something :-)
Then why is the MIA team looking for you? Perhaps you should do it more formally?
Well, I'm using a github-provided tarball, so I'll let my workaround in place: it works nicely.
The .tbz is also provided by GitHub, it is an asset of the release. This is how the dune-release tool works, you probably have the very same thing on other ocaml packages.
I did retire formally a few weeks ago