Skip to content

Conversation

@jankaluza
Copy link
Member

No description provided.

@jankaluza
Copy link
Member Author

jankaluza commented Aug 28, 2025

This does not fix CONTRIBUTING.md section about Dependencies management. I have no idea right now how to do that with monorepo - we would have to research and test. I still plan to do that, but as separate task in another PR, because that will require more time and tests.

Copy link
Member

@lsm5 lsm5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lsm5
Copy link
Member

lsm5 commented Aug 29, 2025

@mtrmac PTAL

Copy link
Contributor

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

I think the “external”, “user-visible” ”identity” of the libraries will now be go.podman.io/*, not the repo, won’t it?


This does not fix CONTRIBUTING.md section about Dependencies management. I have no idea right now how to do that with monorepo - we would have to research and test. I still plan to do that, but as separate task in another PR, because that will require more time and tests.

I would expect it to be substantially unchanged; the instructions will need some updates (and maybe we can assume knowledge of Go modules and remove some of the details).

# Skopeo Roadmap

Skopeo intends to mostly continue to be a very thin CLI wrapper over the [https://github.com/containers/image](containers/image) library, with most features being added there, not to this repo. A typical new Skopeo feature would only add a CLI for a recent containers/image feature.
Skopeo intends to mostly continue to be a very thin CLI wrapper over the [https://github.com/containers/container-libs/tree/main/image](container-libs/image) library, with most features being added there, not to this repo. A typical new Skopeo feature would only add a CLI for a recent containers/image feature.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this say go.podman.io/image?

* Container Storage backends

- [github.com/containers/storage](https://github.com/containers/storage) (Backend for [Podman](https://podman.io), [CRI-O](https://cri-o.io), [Buildah](https://buildah.io) and friends)
- [https://github.com/containers/container-libs/tree/main/storage](https://github.com/containers/container-libs/tree/main/storage) (Backend for [Podman](https://podman.io), [CRI-O](https://cri-o.io), [Buildah](https://buildah.io) and friends)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

go.podman.io/storage?


Note: `skopeo` does not require any container runtimes to be running, to do most of
its functionality. It also does not require root, unless you are copying images into a container runtime storage backend, like the docker daemon or github.com/containers/storage.
its functionality. It also does not require root, unless you are copying images into a container runtime storage backend, like the docker daemon or https://github.com/containers/container-libs/tree/main/storage.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

go.podman.io/storage ? Or just Podman’s storage, or maybe best containers-storage: — the syntax users use.

@github-actions
Copy link

A friendly reminder that this PR had no activity for 30 days.

@mtrmac
Copy link
Contributor

mtrmac commented Sep 29, 2025

@jankaluza friendly ping

@github-actions github-actions bot removed the stale-pr label Sep 30, 2025
@github-actions
Copy link

A friendly reminder that this PR had no activity for 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants