-
Notifications
You must be signed in to change notification settings - Fork 22
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
Support <pkg>.opam files #53
Conversation
Use "<pkg>.opam" files when there are some but no "opam" file is present. This is useful for repositories containing multiple opam packages.
Oh, that's awesome, thanks! I'll also have use for this :) Did you make sure to still support the case of directories ( |
Ah, I didn't know you could do this. I saw the thing about the BTW for new projects, is there any point in using a directory rather than a file? I imagine that the directory is so that you can group the various files ( |
Indeed, but it could still have a use for the |
I added support for Note that the patch looks big, but it is actually much smaller if you read it with a good diff tool: https://github.com/janestreet/patdiff/blob/master/bin/patdiff-git-wrapper |
@AltGr what's the status on this? I will find this functionality to be very useful very soon. |
I backported to the new |
(which explains the spurious warnings on ocaml/opam-repository#8776) |
This seems to work well for |
So far i've done the submits one by one, but submitting multiple packages at once would be great indeed |
Have you decided what to do with this one? |
This PR was for opam-publish 1.0, it's well obsolete; this is all well supported by opam-publish 2.0 :) |
This PR adds support for projects defining multiple opam packages in the same repository.
The behavior is only changed when there is no
opam
file but some<pkg>.opam
files are present. This wayopam-publish
works the same as before for existing users.In the case where there is no
opam
file but there are<pkg>.opam
files,opam-publish prepare
prepares a submission for each<pkg>.opam
. Moreover, if an explicit package name is specified on the command line, it only prepares a submission for<pkg>.opam
. It is an error if an explicit name is specified but there is no corresponding<pkg>.opam
file.I tested the patch to create this PR: ocaml/opam-repository#8776