<div dir="ltr">Yes, that's it. It works fine if I do -k local (which seems the same as -k path, why multiple names for the same option?).<div><br></div><div>I guess this gives a +1 to the view in 1582 that the default should be path-pin. I do often do `opam install` in order to test that my change is correct, so in other words I'm not ready to git commit just yet. That is necessarily the case when the change I'm making is to the opam file itself. Also if I specify a folder path as the pin's target, to me the intuitive result of that is to use the contents of that folder, committed or not. If I specified a folder path appended with ".git#master" (or something like that), then I'd be happy with that resulting in a git-pin.</div>
<div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Aug 17, 2014 at 12:24 PM, Anil Madhavapeddy <span dir="ltr"><<a href="mailto:anil@recoil.org" target="_blank">anil@recoil.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I wonder if you've been bitten by the git/local autodetection. OPAM 1.2b4 spots that the local directory that you're pinning to is a git repository, and turns it into a git remote instead. if you haven't committed the `opam` file to the local git, then it won't be seen by opam.<div>
<br></div><div>Can you try</div><div><br></div><div>opam pin -k local add foo ~/code/foo</div><div><br></div><div>and see if you get the expected behaviour of using the existing opam file?</div><div><br></div><div>This is the OPAM issue for the autodetection:</div>
<div><a href="https://github.com/ocaml/opam/issues/1582" target="_blank">https://github.com/ocaml/opam/issues/1582</a></div><div><br></div><div>If this is indeed your bug, I'm of the firmer notion that this smart probing should be deactivated before the final release.</div>
<div><br></div><div>-a</div><div><br><div><div><div class="h5"><div>On 17 Aug 2014, at 11:16, Ashish Agarwal <<a href="mailto:agarwal1975@gmail.com" target="_blank">agarwal1975@gmail.com</a>> wrote:</div><br></div>
</div>
<blockquote type="cite"><div><div class="h5"><div dir="ltr">I'm trying out 1.2.0-beta4 and wondering what is the correct workflow for local development packages.<div><br></div><div>Say I have a local package `foo` that is not defined in any repository. I put an opam file in the root of the package's source directory, then did `opam pin add foo ~/code/foo`. However, opam doesn't detect the opam file, and instead says "package not defined, would I like to define a new package". At this point you have to answer yes, and opam creates a new opam file, which is not what I want.</div>
<div><br></div><div>Even if the package is defined in a repository, I want opam to detect the opam file in the source directory, not that defined in the repo.</div><div><br></div>The recent platform blog post says opam pin "will generate a new package on the fly by detecting the presence of an opam file within the source repository itself". Where should this opam file be?<div>
<br></div><div>Note I'm trying to simplify my previous workflow, where I would put the opam file in the source directory at the path "opam/packages/foo/foo.master/opam". Then I would first add this as a repo and also pin to this directory. I'm trying to avoid the first part; I shouldn't have to add a repo per package.</div>
<div><br></div></div></div></div>
_______________________________________________<br>opam-devel mailing list<br><a href="mailto:opam-devel@lists.ocaml.org" target="_blank">opam-devel@lists.ocaml.org</a><br><a href="http://lists.ocaml.org/listinfo/opam-devel" target="_blank">http://lists.ocaml.org/listinfo/opam-devel</a><br>
</blockquote></div><br></div></div></blockquote></div><br></div>