I have a package that I’m trying to publish to opam, and (for various reasons) it needs to have a “slightly modified” version of a standard package, available only for the build-step (it doesn’t install it). I put that slight modification out on github in a fork, and my build-script clones that repo.
The Travis step fails, b/c the “git clone” fails trying to get to the network. In retrospect, it seems obvious why one would not want to allow such arbitrary network operations from within a build-environment.
Uh, I can (of course) put a -copy- of the package into the repo, but I’d prefer to not do so; is there any other way to make this work?
[for those who are curious, the project is: https://github.com/chetmurthy/not-ocamlfind ]