Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coq releases opam #18

Merged
merged 2 commits into from
Dec 13, 2015
Merged

Coq releases opam #18

merged 2 commits into from
Dec 13, 2015

Conversation

clarus
Copy link
Contributor

@clarus clarus commented Dec 7, 2015

Instructions to install Coq with OPAM on the download page.

@herbelin
Copy link
Member

herbelin commented Dec 7, 2015

Short remark in passing. When I do

opam info coq

I get:

version: hott
description: HoTT/Coq stable branch

How to do so that we have a more appropriate info about coq? Is this the responsability of the coq.hott package maintainer (no maintainer field actually)? Is this our responsability? Other?

Incidentally, the coq.hott packages is missing many important fields (ocaml, campl5, labgltk constraints, maintainer, authors, ideally homepage, ...).

@clarus
Copy link
Contributor Author

clarus commented Dec 7, 2015

I think you can do opam info coq.8.4.6 to get the information about another version. By the way, the hott version of Coq is not available in the standard repository.

@herbelin
Copy link
Member

Hi Clarus and thanks for your comment. I think that my questions were two.

The first one was about the unclear output of "opam info" and I filled a feature request about it.

The second one is about the policy about submissions of coq packages. Who should we consider is responsible of ensuring the presence of enough fields in the "opam" file of a package? Who should we consider is responsible of the naming of the version of a package so that a package is considered at its due place in the preorder of version numbers?

@clarus
Copy link
Contributor Author

clarus commented Dec 12, 2015

Thanks for your feature request!

For now, the "mandatory" fields (like license or homepage) are verified by the lint.rb program.

No one is officially responsible of naming of versions, but I think we can expect people to be reasonable, at least for the beginning. For the coq.hott issue, we can maybe remove Coq versions which are not corresponding to tags or branches in the main Git repository.

clarus added a commit that referenced this pull request Dec 13, 2015
@clarus clarus merged commit f0d5e2f into coq:master Dec 13, 2015
gares pushed a commit that referenced this pull request Dec 16, 2015
This reverts commit f0d5e2f, reversing
changes made to f2d7a6c.

Note that reverting a merge makes it impossible to re-merge it.
See:
  https://www.kernel.org/pub/software/scm/git/docs/howto/revert-a-faulty-merge.txt
@clarus clarus mentioned this pull request Dec 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants