> 3. release project.0.3.1, keeping project.0.3 unchanged
The problem is that `project.0.3` will be broken for ever, as well as all dependencies that depend on this particular version.
Maybe there is actually some misunderstanding, and we're talking about different things. Just to clarify, are you going to go
through opam-repository and update all archives of old libraries (e.g. sexplib.7.0.5, sexplib.108.00, ...) and remove `<library>.syntax`
findlib library from it? This is what I'm afraid of. And this is what I name "retroactively".
As according to the PR there is nothing like this. If all old archives will be still available, then it is perfectly fine.
> For merlin and oasis we just need to add pa_sexp_conv.syntax, we'll do that.
This is what I'm proposing.
> I don't know bap very well, does it have "sexplib.syntax" hardcoded in its source code or is the same situation as merlin and oasis?
Yep, but it is not a problem to me to fix it. I'm just wondering are there any more packages, that provide build systems, that can have such problems.
Maybe just grepping the opam universe will help in answering this question.