-
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
Submit transaction #38
Comments
@dbuenzli do you envision this maintaining state somehow in a file? 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. |
Where do you propose the state is kept -- a file? Stored where?
…On Thu, Mar 30, 2017, 00:35 Daniel Bünzli ***@***.***> wrote:
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
<#29>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAYfD0iSHwNubHSCBCoqJU7nwZqxuwGOks5rq1tYgaJpZM4IMOnd>
.
|
I'm not proposing an implementation I'm proposing an UI. |
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 |
@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. |
So these are opam-publish transactions on PRs that already exist? |
btw, I have started to use that workaround in mirage packages to allow multi-packages submit. |
As current version allows to give several packages, seems that it is resolved. Feel free to reopen if needed. |
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
The text was updated successfully, but these errors were encountered: