Indeed. just 'publish' sounds a bit funny but why not. opam doesn't support renaming very well. A workflow to have it done transparently to users could be:
- create a new package publish.0.3.1 - create a new empty package opam-publish.0.3.1 that depends on publish.0.3.1 - make publish conflict with earlier opam-publish versions This way an `opam upgrade` can pick up the name change. We can also, of course, keep an alias. > - Anil Madhavapeddy, 05/08/2015 16:43 - > I notice that "opam publish" doesn't autoinstall the plugin (as occurs with > depext). This is because the OPAM package name is "opam-publish" instead of > simply "publish". Should we rename it, or duplicate the package metadata so > that the autoinstallation works? > > -anil > _______________________________________________ > opam-devel mailing list > [email protected] > http://lists.ocaml.org/listinfo/opam-devel _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
