[opam-devel] pinned package not installing dependencies

[Louis Gesbert]

Indeed, that must be the error:
the default behaviour, on the repository, is to just ignore a field when it 
doesn't have the expected format -- to break as little as possible when the 
repository isn't exactly as expected (repository bug, or problem of 
compatibility beteen versions).

This shouldn't, of course, be the case for pinned packages when using an opam 
file from the source or the user -- so that may be a bug in Opam. In any 
case, I would recomment using `--debug` to see what happens.

Best,
Louis Gesbert - OCamlPro


Le mercredi 20 janvier 2016, 21:58:09 David Scott a écrit :
> On Wed, Jan 20, 2016 at 9:34 PM, Tim Cuthbertson <tim at gfxmonk.net> wrote:
> > I've used opam a bunch, but this is the first time I've tried creating
> > my own package. It seems like I must be doing something dumb, but in
> > order to test my package I'm setting up a new opam repository (opam
> > init; opam switch create; then in that switch opam pin
> > <path-to-git-checkout>).
> > 
> > Opam then tries to install `gup` (my package), but doesn't get very
> > far because it doesn't install any of my dependencies! My opam file
> > 
> > looks like:
> >     opam-version: "1"
> >     name: "gup"
> >     version: "0.5.1"
> >     maintainer: "tim at gfxmonk.net"
> >     depends: [
> >     
> >      "batteries"
> >      "cryptokit"
> >      "extunix"
> >      "lwt" { ">=2.5.1" }
> 
> Try changing this line to
> 
>   "lwt" { >= "2.5.1" }
> 
> Cheers,
> Dave
> 
> >      "ocamlfind" {build}
> >     
> >     ]
> >     build: [
> >     
> >      ["make" "-C" "ocaml" "native"]
> >     
> >     ]
> > 
> > A log of the failed build is at:
> > https://gist.github.com/timbertson/5834db27e6d0ce22a86d
> > 
> > As you can see, it doesn't try to install any of my dependencies. I am
> > using the builtin solver instead of aspcud, but I'm assuming the
> > default solver isn't _that_ bad ;).
> > 
> > I also checked that the contents of `gup.opam` inside the opam
> > repository (in packages.dev/gup) looks right, so it shouldn't be due
> > to an out of date opam file.
> > 
> > Any help?
> > 
> > Cheers,
> > 
> >  - Tim.
> > 
> > _______________________________________________
> > opam-devel mailing list
> > opam-devel at lists.ocaml.org
> > http://lists.ocaml.org/listinfo/opam-devel