-
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
Building from scratch | section "Fedora" #157
Comments
@Luap99 need more clarification here |
@Ricky-Tigg I am not sure why you say these do not exist?
All of them install just fine, sure they are alias but that doesn't matter. The dnf install command is valid as is and in case of iptables it doesn't make sense to switch it as there are two variants and it i up to package manger to choose the right one not us. |
Output against which I created this report:
(!) It can be |
@lsm5 any thoughts? |
@Ricky-Tigg Also, what version of Fedora are you using? Looks like different dnf versions might produce different outputs, especially dnf5.
If it helps, we can specify actual package names or add additional cases for different dnf versions. |
RPM distros can simply run `dnf builddep` on `rpm/podman.spec`. That specfile already handles dependencies for all supported versions of Fedora and CentOS Stream so it's a lot simpler than explicitly specifying all dependencies. Resolves: containers#157 Signed-off-by: Lokesh Mandvekar <[email protected]>
RPM distros can simply run `dnf builddep` on `rpm/podman.spec`. That specfile already handles dependencies for all supported versions of Fedora and CentOS Stream so it's a lot simpler than explicitly specifying all dependencies. Resolves: containers#157 Signed-off-by: Lokesh Mandvekar <[email protected]>
RPM distros can simply run `dnf builddep` on `rpm/podman.spec`. 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]>
RPM distros can simply run `dnf builddep` on `rpm/podman.spec`. 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]>
RPM distros can simply run `dnf builddep` on `rpm/podman.spec`. 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]>
|
@Ricky-Tigg thanks. #174 should just work (TM) as it's being continuously tested with all active versions of fedora and centos stream. That PR depends on containers/podman#19214 which should be going in anytime now. |
Lucky RPM-users; Thank you. |
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. Most of the runtime dependencies are handled in the containers-common-extra package, which simplifies things further for the user. Resolves: containers#157 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]>
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. Most of the runtime dependencies are handled in the containers-common-extra package, which simplifies things further for the user. Resolves: containers#157 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]>
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]>
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. Most of the runtime dependencies are handled in the containers-common-extra package, which simplifies things further for the user. Resolves: containers#157 Signed-off-by: Lokesh Mandvekar <[email protected]>
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. Most of the runtime dependencies are handled in the containers-common-extra package, which simplifies things further for the user. Resolves: containers#157 Signed-off-by: Lokesh Mandvekar <[email protected]>
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]>
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]>
Hello. At https://podman.io/docs/installation#building-from-scratch, which seems to apply to Fedora, the packages go, iptables and pkgconfig do not exist in Fedora's repositories. However their equivalent could exist; here are those that could be such ones:
Of course that would require confirmation from one of yours. If confirmed, the whole amount of packages required for installation could be selected as follows (compacted variant):
It is unclear whether the installation of the packages mentionned as part of the installation command that follows the comand text
make package-install
must be operated before the execution of that command.The text was updated successfully, but these errors were encountered: