Switch from --release to -p in build command

With the introduction of package management dune build --release is going to start using lockfiles (if present) to install dependencies before building the project. Thus in opam file it's recommended to use dune build -p <name> instead, as this will continue to ignore lockfiles.

Signed-off-by: Stephen Sherratt stephen@sherra.tt

For some context, see https://github.com/ocaml/dune/pull/11378

That basically means that from now we have to list every single subpackage of Frama-C in the install command? So that every time we add a new plug-in we have to modify the installation file and to hope that no one will forget to do it ...

Thank you for reaching for us. As I asked in the linked issue, can we still use --ignore-lock-dir ?

Ah yes --ignore-lock-dir would also work here and not require listing all the package names. I'll update this patch.

Ah that doesn't work at the moment. --release currently implies --ignore-lock-dir (https://github.com/ocaml/dune/pull/11378 would change this), and this means that you can't pass both flags at the same time. I'll post on the linked PR as we may need to change our approach.

Just to clarify our position about the option -p: for us it is currently unusable.

assigned to @blanchard

I can think of two alternatives:

• frama-c continues to use --release but if the project ever starts using dune package management you'll need to make sure that released source archives don't contain lockdirs
• in the build commands, check the version of dune and if it's >= the version that switches the behaviour of --release, pass --ignore-lock-dir to dune build.

Ok, so I guess option 1 is perfect for us since we have no plan to use dune package management.