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

Submit transaction #38

Closed
dbuenzli opened this issue Apr 21, 2016 · 10 comments
Closed

Submit transaction #38

dbuenzli opened this issue Apr 21, 2016 · 10 comments

Comments

@dbuenzli
Copy link

This should be designed with #29 in mind. Sometimes you'd like to submit a set of packages in a single submission otherwise the repo may be in an inconsistant state at some commits.

Something like

opam publish submit --add PKG1
opam publish submit --add PKG2
opam publish submit --commit
@tekknolagi
Copy link

@dbuenzli do you envision this maintaining state somehow in a file? Why not just prepare/add all at once?

@dbuenzli
Copy link
Author

Why not just prepare/add all at once?

I think it will make things painful if you need to correct and resubmit, also all at once will be difficult to solve with #29.

@tekknolagi
Copy link

tekknolagi commented Mar 30, 2017 via email

@dbuenzli
Copy link
Author

Where do you propose the state is kept

I'm not proposing an implementation I'm proposing an UI.

@dbuenzli
Copy link
Author

But given what I wrote in #29 I think a file format should be defined that allows to describe changes to an opam repo (constraints updates + paths to new packages to add) and that the tool should then consume these files to update the repo in a single commit. No state needs to be kept by opam-submit itself.

@tekknolagi
Copy link

I think it will make things painful if you need to correct and resubmit

@dbuenzli wouldn't you have ordinarily done your checks and corrections after the preparation stage? So this is just uploading a PR?

@dbuenzli
Copy link
Author

dbuenzli commented Mar 30, 2017

@dbuenzli wouldn't you have ordinarily done your checks and corrections after the preparation stage? So this is just uploading a PR?

Maintainers and bots may think badly about your PR.

@tekknolagi
Copy link

So these are opam-publish transactions on PRs that already exist?

@samoht
Copy link
Contributor

samoht commented Jun 22, 2017

btw, I have started to use that workaround in mirage packages to allow multi-packages submit.

@rjbou
Copy link
Contributor

rjbou commented Apr 28, 2020

As current version allows to give several packages, seems that it is resolved. Feel free to reopen if needed.
Thanks!

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

No branches or pull requests

4 participants