-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Make gvproxy path configurable with containers.conf #11449
Make gvproxy path configurable with containers.conf #11449
Conversation
I've been reading through the Issue and PR history of this particular PR and two things strike me:
Having said that, we may still need the quick fix to fall back to |
It definitely does, though... |
@Conan-Kudo It does, but that directory not user-writable on recent OS releases, and even if it were, installing to System directories flies in the face of Homebrew's philosophy. I think longer-term, |
@simnalamburt create different search methods by OS (i.e. Linux and Darwin) and we can have a different approach in each. I personally see no issue with the code in 3.3; it just didnt get into main branch yet. Good luck, ill try to check back but im on PTO. |
Perhaps we should consider something like this: jonpspri@562c720 Rather than do backflips in the code, the build process can set the path as a variable. I think in 95% of cases, the target should be known at build time. For example, I updated my Homebrew install to do Otherwise, I expect we should start looking to an entry in ~/.config/podman. Dunno what the configuration libraries are... Thoughts? (p.s. In the next revision, I'll likely use |
I also read up on the Homebrew standards for installs. Homebrew reserves |
From my reading of the docs, the |
@pharaujo I like it. Install into the Keg libexec and use a build-time configuration to direct podman to it. So the make becomes
I've tested with my formula at https://github.com/jonpspri/homebrew-core/blob/master/Formula/podman.rb while we sort out Pull Requests. |
Presented as an alternative to PR containers#11449 Rather than do backflips in the code to locate `gvproxy`, use a build-time variable to set the location. That variable can default to `/usr/libexec` but other build packages (_e.g._ Homebrew) can set it to something of their liking. I'll take no offense if the consensus is that we do not want to pollute the build, but we should likely add a runtime configuration parameter as an alternative in that case. Fixes: containers#11226 Signed-off-by: Jonathan Springer <[email protected]>
We need a consensus. Current options:
Which option do you prefer? I'd prefer option 5. |
@simnalamburt I'm also on board for option 5 (as done over in containers/common#758 ). |
Oh I didn't notice the progress of over there. Knowing that it is set to option 5, I will find out what I can do to help. |
@simnalamburt One thing you could whip out if you have time is that even once containers/common#758 is merged, we'll still need to refer to the config item in the code this PR addresses. Could you put that together in this PR? |
Sure I’ll watch for that PR!
2021년 9월 10일 (금) 02:37, Jonathan Springer ***@***.***>님이 작성:
… @simnalamburt <https://github.com/simnalamburt> One thing you could whip
out if you have time is that even once containers/common#758
<containers/common#758> is merged, we'll still
need to refer to the config item in the code this PR addresses. Could you
put that together in this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11449 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABB235JYU7DMATM45QB4Y6LUBDWE5ANCNFSM5DNOLQMA>
.
|
NOTE: This PR is waiting for the new release of https://github.com/containers/common |
@simnalamburt You can vendor in the main branch. |
The new code is merged into podman #11552. If you rebase you should be able to use |
@simnalamburt thanks for your contribution ... can you pleasse rebase this PR and updated with the new method call? |
Ok I will |
/approve |
and then of course, we will merge it |
Sorry for the delay, it’s 04:30 AM in KST. I’ll do it in few hours later
2021년 9월 14일 (화) 04:27, Brent Baude ***@***.***>님이 작성:
… Ok I will
and then of course, we will merge it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11449 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABB235LKWDBUYU2N2IV3U7TUBZGCJANCNFSM5DNOLQMA>
.
|
98418aa
to
13609ff
Compare
13609ff
to
107f06e
Compare
I've updated and rebased the PR. BTW, this is the last piece that is needed for podman's Apple Silicon support by default. Yay! |
@simnalamburt You also have to add |
Closes containers#11531 [NO TESTS NEEDED] Signed-off-by: Hyeon Kim <[email protected]>
107f06e
to
072b061
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: baude, Luap99, rhatdan, simnalamburt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
macOS does not have
/usr/libexec/
so we look in the executable paths first.Closes #11226
Closes #11531
Blocked by containers/common#758
NOTE: This PR is identical with #11234. Since #11226 still exist in the main branch, I'm sending the PR again.