{"action":"created","issue":{"url":"https://api.github.com/repos/ocaml/opam/issues/2531","repository_url":"https://api.github.com/repos/ocaml/opam","labels_url":"https://api.github.com/repos/ocaml/opam/issues/2531/labels{/name}","comments_url":"https://api.github.com/repos/ocaml/opam/issues/2531/comments","events_url":"https://api.github.com/repos/ocaml/opam/issues/2531/events","html_url":"https://github.com/ocaml/opam/issues/2531","id":150946064,"number":2531,"title":"Next: opam compiler-conf doesn't work anymore","user":{"login":"Drup","id":801124,"avatar_url":"https://avatars.githubusercontent.com/u/801124?v=3","gravatar_id":"","url":"https://api.github.com/users/Drup","html_url":"https://github.com/Drup","followers_url":"https://api.github.com/users/Drup/followers","following_url":"https://api.github.com/users/Drup/following{/other_user}","gists_url":"https://api.github.com/users/Drup/gists{/gist_id}","starred_url":"https://api.github.com/users/Drup/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Drup/subscriptions","organizations_url":"https://api.github.com/users/Drup/orgs","repos_url":"https://api.github.com/users/Drup/repos","events_url":"https://api.github.com/users/Drup/events{/privacy}","received_events_url":"https://api.github.com/users/Drup/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2016-04-25T18:33:07Z","updated_at":"2016-07-26T19:38:38Z","closed_at":null,"body":"[opam-compiler-conf](https://github.com/gasche/opam-compiler-conf) works by creating a compiler in `~/.opam/compilers/`. It doesn't work with opam 2.0, since compilers are packages now. My initial tentative was to put the compiler in `~/.opam/packages/ocaml/`, like in the `next` branch of opam-repository, but it doesn't work either. What should I do ?\r\n\r\ncc @gasche "},"comment":{"url":"https://api.github.com/repos/ocaml/opam/issues/comments/235380796","html_url":"https://github.com/ocaml/opam/issues/2531#issuecomment-235380796","issue_url":"https://api.github.com/repos/ocaml/opam/issues/2531","id":235380796,"user":{"login":"gasche","id":426238,"avatar_url":"https://avatars.githubusercontent.com/u/426238?v=3","gravatar_id":"","url":"https://api.github.com/users/gasche","html_url":"https://github.com/gasche","followers_url":"https://api.github.com/users/gasche/followers","following_url":"https://api.github.com/users/gasche/following{/other_user}","gists_url":"https://api.github.com/users/gasche/gists{/gist_id}","starred_url":"https://api.github.com/users/gasche/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gasche/subscriptions","organizations_url":"https://api.github.com/users/gasche/orgs","repos_url":"https://api.github.com/users/gasche/repos","events_url":"https://api.github.com/users/gasche/events{/privacy}","received_events_url":"https://api.github.com/users/gasche/received_events","type":"User","site_admin":false},"created_at":"2016-07-26T19:38:38Z","updated_at":"2016-07-26T19:38:38Z","body":"That's very nice (nitpick: I don't understand the name `ocaml-variants`). I still think that a scripting layer (that is, `compiler-conf`) is useful to infer the `version` variable from the compiler's version plus the DCVS branch name (I'm pretty sure you would forget to update your opam file when you checkout to a new branch), similarly to generate the switch name, and to provide the safety-checking of making sure that branch did not change under your feet -- a fairly common mistake when playing between branches in git.\r\n\r\nAlso, the `install` rule you use (without `build` rule) are suitable for the development workflow, but not for user-destined packaging, and it breaks the opam conventions. I would expect people cloning the git repository to expect `opam pin add ocaml .` to just work -- which means that there should probably be a message clarifying this if you want to include it upstream."}}
{"actor":{"display_login":"gasche"}}