-
Notifications
You must be signed in to change notification settings - Fork 369
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
*: gating different drivers behind build tags #296
Comments
I'm +1 on this. |
It actually is possible now, with #290 . (To be fair, vendored into
(As a side note, many users of the library who need only specific transports can import only those transports and minimize dependencies. Only explicitly pulling in I’m fine with allowing to opt out of the transports with non-trivial dependencies; I would be less enthusiastic (though probably could still be persuaded) about a blanket policy of making all transports optional, even the self-contained ones like |
Ah, I didn't see that PR @mtrmac. But yes, my suggestion only applies for things with non-trivial dependencies. |
I believe we have this now, and this is a rather old issue, I am closing please reopen if you think we should still work on this. |
I'm not sure if we've discussed this before, but if we want to have a library that implements all manner of image formats and schemes we need to make it possible for users of this library to opt out of the dependencies if they're not going to use a particular driver.
For example, if I want to build
skopeo
withoutostree
support that is currently not possible. Should we addnoostree
and similar buildtags to each of the image schemes? Or do you feel that'll cause issues?The text was updated successfully, but these errors were encountered: