-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
gles3 initial versions #5894
gles3 initial versions #5894
Conversation
gles3.20160307.alpha - via opam-publish
✅ All lint checks passed 3c463e9
✅ Installability check (4577 → 4578)
|
I see that some test fails ... but I can't access any details ... How can I know what's happening , |
I think if you click On Linux:
On OS X:
|
"Christophe Raffalli <[email protected]>, Alexandre Miquel<[email protected]>" | ||
homepage: "http://lama.univ-savoie.fr/~raffalli/gles3" | ||
bug-reports: "[email protected]" | ||
license: "LGPL" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please specify the version of the LGPL license and whether you intend to use the "OCaml linking exception"?
Please see the other comments on #5893. Also, you can simply force-push to a branch that is the source of a pull request to update it instead of creating a new branch and a new pull request. This helps to keep the conversation about the PR in one place and reduce the volunteer effort required to review submissions. |
I did not see all comment, sorry. packages/gles3/gles3.20160307.alpha/url
I believe this can be archive: in order to maintain flexibility in transport. |
It is very minor but With all that said, lots of other packages use |
... and I see that this is probably an opam-publish issue. Sorry to bother you, @craff. |
I have stopped to use opam-publish ... to me it should just git commit to your own fork of the opam-repository ... The pull request can be manual ... My changes are coming soon |
This is normal if GLES3 is not installed on the machine ? |
This looks to me like a wrong ocaml installation ... moreover, I do not expect gles3 to work on OSX so easily ? |
For the missing header, what we usually do is a second "configuration" package, that checks the header avaibility and provides information about the corresponding "system package" on usual distros. See for instance: https://github.com/ocaml/opam-repository/blob/master/packages/conf-cairo/conf-cairo.1/opam In particular, the |
If the library is not supposed to compile on OS X, you might add |
I think the package should be ok ... except that I don't know how to produce the depexts for all distribution on earth ;-) |
You already added quite a few distro in Unfortunatly, the CI failed because the header file Thanks again for submitting the package ! |
@OCamlPro-Henry you are correct. LGTM. |
Oh, one last thing, it might be nice to include a |
I've open ocaml-opam/Camelus#7 to track the |
I added post-messages. We can not ask a minimal version in depexts ? This would make |
Unfortunately, we don't currently have versioning incorporated into the depext system due to complexity of the interface task. Some level of this kind of functionality is certainly possible and I have open ocaml-opam/opam-depext#43 to track that. |
s/or/os/ done |
By the way, the typo s/or/os did not give an error when I installed the package from by own |
No error is generated because |
Is the package OK now or do you have more suggestion ? |
Thanks ! |
LGTM, thanks for introducing the |
And thanks again for all the help with opam ... As an aside question: opam2debian is still alive ? It is not in the opam repository. I think tools like opam2x One could even imagine that all opam package automatically become package for |
I restarted from a fresh fork ... and now have a clean patch (I hope)