Yeah, we generally do have a more powerful engine underlying OPAM, so I can see the difficulties here...
-anil > On 5 Oct 2015, at 01:54, Louis Gesbert <[email protected]> wrote: > > Well, `opam pin add --dev type_conv` is a bit more verbose, but it will > prompt for install or upgrade with a single command. It could be possible to > install the dev version as a one-shot, without pinning, but I don't think > that would be a good idea, since opam will likely want to downgrade it on any > later upgrade or if needing recompilation... > >> - Anil Madhavapeddy, 04/10/2015 17:40 - >> On 3 Oct 2015, at 11:53, Daniel Bünzli <[email protected]> wrote: >>> >>> Le jeudi, 1 octobre 2015 à 17:59, Anil Madhavapeddy a écrit : >>>> [ ["osx" "homebrew"] ["tap/package"] ] >>>> >>>> In fact, would that just work as-is? >>> For the record, yes it does. It seems that brew is even able to find were >>> the tap lies and automatically add it. In my case it ended up being >>> tap/formulae/package (armmbed/formulae/arm-none-eabi-gcc) but that may be >>> due to the way the tap is structured. >> >> Great! I wonder if there's a lesson there for OPAM. I could imagine having >> an auto-fork shortcut so that you could do: >> >> $ opam install janestreet/type_conv >> >> to get their latest tap. I guess our equivalent is an explicit URL, which >> is much more flexible, but sadly more verbose due to the need for a separate >> pin step rather than a single installation instruction. >> >> -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 > _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
