On 27 Aug 2015, at 05:57, Louis Gesbert <[email protected]> wrote: > >> - Anil Madhavapeddy, 26/08/2015 18:49 - >> One thing I noticed is that the automatic plugin installation doesn't >> play well with non-interactivity (e.g. -y), btw. > > It should work with `OPAMYES=1` ; it's otherwise a bit difficult to parse the > command-line arguments that are normally directed towards a different program. > > Or should we allow something like `opam -y publish` ? Or normalise the > arguments a plugin is supposed to accept ?
This does bite me quite often, since (for example) "opam depext -i -j 4 -y foo" doesn't work -- i.e. `opam depext -i` is no longer a dropin replacement for `opam install` even though semantically it's meant to just augment the installation process with an external dependency check. One way to get around this would be to make the cmdliner structures available for plugins to link against in opam-lib. The global ones especially could be used by every plugin and passed through to OPAM subcommands by setting the right environment variables (perhas https://github.com/dbuenzli/cmdliner/issues/23 would be of use for that). -anil _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
