Handle multiple packages with multiple names

[dinosaure]

Since #327, it's not possible to pass a name which can differ from the given dune-project. ocaml-git has multiple packages and their release cycles are not the same. Currently, I try to release carton and dune-release creates a git-3.4.0.tbz which is not recognized by dune-release publish then (because 3.4.0 is not the right version of carton - which is 0.4.3).

It's possible to keep the name option?

[dinosaure]

Note that --pkg-version does not change the tbz produced.

[NathanReb]

One quick workaround you can use atm is to pass the --dist-file <path-to-tarbal> option to publish so that it doesn't try to find the tarball on its own.

Handling repositories that have multiple packages is not well specified atm, even more so if they use different versioning. Properly handling this will require specification and likely proper support in other tools as well, such as dune. You can consider that at the moment, having multiple packages that don't use the same versions is not officially supported by dune-release. You might be able to make it work using some options but until we have fully specified how we want to support this across all our tools, we can't fully support it by default.

I'm happy to further discuss this with you to better understand your requirements so we can figure out how this should all work in the future!