-
Notifications
You must be signed in to change notification settings - Fork 52
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
installation.md: simplify build-from-source for rpm distros #174
Conversation
This should go in only after containers/podman#19214 is merged. |
95fba4a
to
f2fffb1
Compare
hmm, |
@TomSweeneyRedHat @Luap99 @rhatdan PTAL @Ricky-Tigg the podman PR is merged. Please feel free to try the updated steps in this PR if you'd like. |
@cgiradkar PTAL |
err ... looking at the title |
do we |
fetching install time dependencies directly from the spec file and avoiding |
I think most folks will be looking to do 'make'. Instead of "Building from Scratch", I'd be OK with "Building from Source" if you think that's better. |
If I just look at the current list I see several packages that are missing and/or should not be there. Thus I like the dnf builddep and dnf install podman because well we know that the rpm spec is always correct otherwise it would not build. But then again we have the same problem on debian/ubuntu so maybe we should allocate someone to keep this in sync. Also the normal make commands are listed under |
ack, I'll revise it this way then:
I can leave a note in |
So, Are we ok with limiting the RHEL steps to rhel 9 / c9s ? I have separated Fedora out from RHEL and CentOS Stream already as containers-common-extra is only on Fedora and RHEL/centos needs additional repos enabled. |
@Luap99 @TomSweeneyRedHat ping, wdyt ? |
Well the current instructions (listed packages) already do not work for RHEL so this would not be a new problem. I would love to have some basic instruction on how to build on RHEL 8 as I had to test some of my patches there in the past and it was difficult to figure out how to get the right deps. However I won't block over it. If RHEL 9 works than I see this already as good improvement. |
@lsm5 I'd say no copr. I'm OK with providing instructions for RHEL9 only, but maybe we can add "try at your own risk" kind of verbiage for RHEL 8. |
ack, I'll do Fedora, RHEL 9, CentOS 9, followed by RHEL 8, CentOS 8, so 3 sections. |
just a quick friendly @lsm5 ping to put this back on the radar |
oops, yup. Let me get on this one. The go-md2man issue has gone away so things are a little simpler now. |
Include dependencies in rpm/podman.spec to make it easy for end users to build podman from source. This way users can install all build dependencies by running `dnf -y builddep rpm/podman.spec`. This is not usually noticeable except on container environments where man-db often isn't installed by default. Refs: containers/podman.io#157 containers/podman.io#174 [NO NEW TESTS NEEDED] Signed-off-by: Lokesh Mandvekar <[email protected]>
blocking on containers/podman#19670 |
Updated PR. Have separate instructions for CentOS Stream, RHEL 8 and 9. RE: RHEL 8 and 9, I have yet to verify that on RHEL machines. The repos on rhel containers don't find the shadow-utils-subid-devel and ostree-devel packages. I'll get back to this Monday. |
Include dependencies in rpm/podman.spec to make it easy for end users to build podman from source. This way users can install all build dependencies by running `dnf -y builddep rpm/podman.spec`. This is not usually noticeable except on container environments where man-db often isn't installed by default. Refs: containers/podman.io#157 containers/podman.io#174 [NO NEW TESTS NEEDED] Signed-off-by: Lokesh Mandvekar <[email protected]>
Include dependencies in rpm/podman.spec to make it easy for end users to build podman from source. This way users can install all build dependencies by running `dnf -y builddep rpm/podman.spec`. This is not usually noticeable except on container environments where man-db often isn't installed by default. Refs: containers/podman.io#157 containers/podman.io#174 [NO NEW TESTS NEEDED] Signed-off-by: Lokesh Mandvekar <[email protected]>
tried this on an internal rhel instance and the CRB and appstream repos were able to find all required packages. I'm not sure if a public RHEL instance with developer subscription or such will have access to the exact same repos, but we can cross that bridge later. @TomSweeneyRedHat @Luap99 Good for another review. |
One small suggestion for consideration, otherwise LGTM |
RPM distros can simply run `dnf builddep` on `rpm/podman.spec` to fetch build dependencies. That specfile already handles dependencies for all supported versions of Fedora and CentOS Stream so it's a lot simpler and easier to maintain than duplicating dependency specification in the documentation. Resolves: containers#157 Signed-off-by: Lokesh Mandvekar <[email protected]>
@TomSweeneyRedHat @Luap99 PTAL again. I simplified the |
lgtm |
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
@lsm5 very nice rework btb, TYVM! |
RPM distros can simply run
dnf builddep
onrpm/podman.spec
. Thatspecfile already handles dependencies for all supported versions of
Fedora and CentOS Stream so it's a lot simpler and easier to maintain
than duplicating dependency specification in the documentation.
Resolves: #157