Why not set `opam-version` in the package to something greater than 1.2 to avoid the package from being used there ? Isn't it the goal of that field ?
Deprecating a whole version probably still used by some users sounds quite overkill just to fix one package. --Fabrice On Wed, Jul 6, 2016 at 10:29 AM Thomas Gazagnaire <tho...@gazagnaire.org> wrote: > I think it is time to deprecate opam 1.2.0. What do you think? > > See https://github.com/ocaml/opam-repository/pull/6888 for a recent > issue: it doesn’t understand the `pinned` variable. This could be fixed by > adding a rewriting layer between 1.2.2 and 1.2.0 and adding a redirection > based on the version number (we already do that for opam 1.1) but that’s a > lot of efforts for not much gains. So I’m in favour of simply not > supporting 1.2.0 anymore. > > If you are still using 1.2.0 please complain now :-) > > Thomas > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-devel >
_______________________________________________ opam-devel mailing list opam-devel@lists.ocaml.org http://lists.ocaml.org/listinfo/opam-devel
