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

main: adapt for a multicall binary, then move ostree_ext CLI to it #3277

Closed
lucab opened this issue Dec 14, 2021 · 0 comments · Fixed by #3281
Closed

main: adapt for a multicall binary, then move ostree_ext CLI to it #3277

lucab opened this issue Dec 14, 2021 · 0 comments · Fixed by #3281
Labels
jira for syncing to jira

Comments

@lucab
Copy link
Contributor

lucab commented Dec 14, 2021

Right now rpm-ostree is re-exporting a subset of ostree-ext CLI entries, specifically only the container bits:

"ex-container" => {
return rpmostree_rust::container::entrypoint(&args_borrowed).await;

In the context of ostreedev/ostree#2480, we should tweak rpm-ostree into a multicall binary and map the whole ostree-ext surface, by dispatching based on argv[0].
That would also free the rpm-ostree ex-container verb for things like #3276, if needed.

@lucab lucab added the jira for syncing to jira label Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira for syncing to jira
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant