-
Notifications
You must be signed in to change notification settings - Fork 83
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
Provide libraries #2
Comments
On Thu, Sep 15, 2016 at 07:56:49AM -0700, Antonio Murdaca wrote:
Work in that direction in opencontainers/image-spec#159 ;). Should I |
we need to slightly refactor the code at least according to opencontainers/image-spec#234 (comment) before taking into consideration opencontainers/image-spec#159 (there has been no consensus in there also) IMO |
On Thu, Sep 15, 2016 at 08:31:38AM -0700, Antonio Murdaca wrote:
I already have a callback-based ref walker [1,2](following a @stevvooe |
I think libraries with fairly stable APIs would be great! Unpacking can be error-prone, signature validation (once it becomes part of the spec) is not code you want to write yourself and anything that has to do with CAS would be good to share. For all these reasons I would love OCI to expose this functionality through reusable and configurable Go APIs in addition to the CLIs. |
@runcom Go doesn't have "libraries" - it has packages. ;) Indeed, the goal is to provide rich APIs, but I don't think we are even close to a point where we can stabilize an API. The current code is fine for purpose, but I don't think the interface is flexible enough to stand the test of time. |
On Thu, Sep 15, 2016 at 12:33:24PM -0700, Stephen Day wrote:
Possibly true, but you have to start somewhere ;). |
Agree with @wking, starting somewhere and defining a versioned API shouldn't hurt anyone. We can't just wait because we're not at the point to fully stabilize (other projects broke backward compatibility, libraries break compatibility at almost each major release..).
Yet are libraries to me, but whatever |
is there progress on this? someone want to own this? |
|
I can dip my toe in, but probably not until late next week; not sure what
the timeline is like.
…On Thu, Mar 9, 2017 at 3:20 PM, Aleksa Sarai ***@***.***> wrote:
umoci's interfaces are already split up into packages (and I'm currently
doing more cleanups in this area in preparation for the merge of the
libraries into this project).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABJ6xL27Gezb1sdhYZweMRH7uu5z3VBks5rkIkvgaJpZM4J9-AM>
.
|
I'm currently planning on implementing So there are the current things I wouldn't mind getting a hand with (though the |
Looking forward to seeing the umoci stuff merging in. |
this project could/should provide libraries around the commands' functionalities so people can write additional tooling.
The text was updated successfully, but these errors were encountered: