tarides
`dune-release tag` with multiple packages does not work
With dune-release.1.4.0 and with a distribution with multiple packages (such as https://github.com/dinosaure/art, see art and rowex), it's not possible to properly ask dune-release to make a Git tag:
$ dune-release tag
dune-release: [ERROR] cannot determine name automatically: use `-p <name>`
$ dune-release -p art tag
dune-release: too many arguments, don't know what to do with `tag'
Usage: dune-release COMMAND ...
Try `dune-release --help' for more information.
$ dune-release tag -p art
dune-release: unknow option `-p'.
Usage: dune-release tag [OPTION]... [VERSION]
Try `dune-release tag --help'or `dune-release --help' for more information.
The tag is for the whole repo and given most tools use tags to determine the version (dune for instance with dune subst) all packages in the same repo have to follow the same versioning, that's why dune-release tag for the whole repo and not per package as there is no such thing as per package tagging.
You can run dune-release tag and then release only a subset of the repositosy's package, i.e. skip that version for the other packages.
I agree it is not ideal not to be able to version packages in the same repo differently and we could work out a scheme for that to work but we need to agree on it across all the tools first unfortunately.
