Skip to content

Conversation

@Leonidas-from-XIV
Copy link
Collaborator

Pulled out of #13176.

Signed-off-by: Marek Kubica <marek@tarides.com>
eval_url package.url
>>= (function
| None -> opam_package stack package
| None -> pinned_via_opam stack package
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rgrinberg What I don't understand here is why this is calling the opam code path despite package.origin stating Dune?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The suggestion here should clarify it #13176 (comment)

Because what is Opam | Dune here is not the type of package but the type of pin that we have. And we can pin both types of packages with both types of pins.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be more precise:

  • a dune package may have both opam pins and pin stanzas

  • an opam package may only have opam pins

  • A pin stanza may refer to a dune or an opam package

  • An opam file pin may refer to a dune or an opam package as well

Signed-off-by: Marek Kubica <marek@tarides.com>
@rgrinberg rgrinberg merged commit 02ebab6 into ocaml:main Jan 2, 2026
30 checks passed
@Leonidas-from-XIV Leonidas-from-XIV deleted the refactor-pinning-names branch January 3, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants