diff --git a/podman.spec b/podman.spec index b67cf09..ae44648 100644 --- a/podman.spec +++ b/podman.spec @@ -75,6 +75,7 @@ Requires: containers-common Requires: containernetworking-plugins >= 0.7.3-2 Requires: iptables Requires: nftables +Recommends: podman-manpages = %{epoch}:%{version}-%{release} Recommends: container-selinux Recommends: slirp4netns >= 0.3-0 Recommends: fuse-overlayfs >= 0.3-8 @@ -182,9 +183,12 @@ Provides: bundled(golang(k8s.io/kube-openapi)) = 275e2ce91dec4c05a4094a7b1daee55 Provides: bundled(golang(k8s.io/utils)) = 258e2a2fa64568210fbd6267cf1d8fd87c3cb86e %description +Podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool. Podman provides a Docker-CLI comparable command line that eases the transition from other container engines and allows the management of pods, containers and images. Simply put: alias docker=podman. Most Podman commands can be run as a regular user, without requiring additional privileges. + +Podman uses Buildah(1) internally to create container images. Both tools share image (not container) storage, hence each can use or manipulate images (but not containers) created by the other. + %{summary} -%{repo} provides a library for applications looking to use -the Container Pod concept popularized by Kubernetes. +%{repo} Simple management tool for pods, containers and images %package docker Summary: Emulate Docker CLI using podman @@ -387,6 +391,7 @@ ln -s ../../../../ src/%{import_path} popd ln -s vendor src export GOPATH=$(pwd)/_build:$(pwd) +PODMAN_VERSION=%{version} %{__make} PREFIX=%{buildroot}%{_prefix} ETCDIR=%{buildroot}%{_sysconfdir} podman-remote export BUILDTAGS="varlink seccomp exclude_graphdriver_devicemapper $(hack/btrfs_installed_tag.sh) $(hack/btrfs_tag.sh) $(hack/libdm_tag.sh) $(hack/ostree_tag.sh) $(hack/selinux_tag.sh)" %gogenerate ./cmd/%{name}/varlink/... %gobuild -o bin/%{name} %{import_path}/cmd/%{name} @@ -498,7 +503,6 @@ cp -pav test/system %{buildroot}/%{_datadir}/%{name}/test/ %license LICENSE %doc README.md CONTRIBUTING.md pkg/hooks/README-hooks.md install.md code-of-conduct.md transfer.md %{_bindir}/%{name} -%{_mandir}/man1/podman*.1* %{_mandir}/man5/*.5* %{_datadir}/bash-completion/completions/* # By "owning" the site-functions dir, we don't need to Require zsh @@ -529,6 +533,33 @@ cp -pav test/system %{buildroot}/%{_datadir}/%{name}/test/ %doc README.md CONTRIBUTING.md pkg/hooks/README-hooks.md install.md code-of-conduct.md transfer.md %endif +%package manpages +Summary: Man pages for the podman commands +BuildArch: noarch + +%files manpages +%{_mandir}/man1/podman*.1* + +%description manpages +Man pages for the podman commands + +%package remote +Summary: (Experimental) Remote client for managing podman containers +Recommends: podman-manpages = %{epoch}:%{version}-%{release} + +%description remote +Remote client for managing podman containers. + +This experimental remote client is under heavy development. Please do not +run podman-remote in production. + +podman-remote uses the varlink connection to connect to a podman client to +manage pods, containers and container images. Podman-remote supports ssh +connections as well. + +%files remote +%{_bindir}/podman-remote + %triggerpostun -- %{name} < 1.1 %{_bindir}/%{name} system renumber exit 0