-
Notifications
You must be signed in to change notification settings - Fork 9
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
Transform oasis2opam into an OASIS command plugin of OASIS #33
Comments
I am not against it. What route should we follow for integration? Also, this will entail some changes to OASIS because, for example, functions added to |
Here is the "documentation": There is an example in the documentation. You probably don't need to change anything in OASISVersion, because you can keep the exact same structure, except that you'll have an extra library. I can actually send you a PR with a little bit of shuffling around to create the plugin -- if you can wait for it. |
Ah, OK. I misunderstood, I thought you wanted |
My code depends on
|
Can you publish your version to a branch, so that I can test it myself ? unrelated: can we discuss the '2opam' name, I would vote for to-opam or opam-convert... |
On 2016-12-12, Sylvain Le Gall wrote:
Can you publish your version to a branch, so that I can test it
myself ?
unrelated: can we discuss the '2opam' name, I would vote for to-opam
or opam-convert...
I'd like to keep it reasonably short, so "to-opam" is OK with me.
|
Solved: You can pin the dev-repo in a few hours when opam/testing will be promoted. |
It sort of works but I get a segfault if the state has to be synchronized. Way to reproduce:
The same happens when trying to generate the files
I haven't investigated but may it be due to the |
Tracking bug: I will fix it for OASIS 0.4.9, expect to have to test a few version to make sure it is working before the release. |
OK. Keep me posted about your progress — I can pin oasis when you are ready to test if you like. |
oasis2opam
is tightly linked to OASIS and we should make sure it is always in sync withoasis
. One way to achieve that, is to make it a plugin of OASIS. In this case we will be sure that the parsing of_oasis
files is up to date.I have been hit by this bug a few time, because oasis2opam was using an old parser from OASIS that didn't handled some special features (like AlphaFeatures and BetaFeatures introduced recently).
The text was updated successfully, but these errors were encountered: