| 1 | Summary: CNI network plugins |
| 2 | Name: containernetworking-plugins |
| 3 | Version: 0.9.1 |
| 4 | Release: 1 |
| 5 | License: Apache v2.0 |
| 6 | Group: Applications/System |
| 7 | #Source0Download: https://github.com/containers/podman/releases |
| 8 | Source0: https://github.com/containernetworking/plugins/archive/v%{version}/%{name}-%{version}.tar.gz |
| 9 | # Source0-md5: d28bcf99557ac61a55445a0e5a44f5b1 |
| 10 | URL: https://github.com/containernetworking/plugins/ |
| 11 | BuildRequires: golang |
| 12 | BuildRequires: rpmbuild(macros) >= 2.005 |
| 13 | ExclusiveArch: %{ix86} %{x8664} %{arm} aarch64 mips64 mips64le ppc64 ppc64le s390x |
| 14 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) |
| 15 | |
| 16 | %define _debugsource_packages 0 |
| 17 | |
| 18 | %description |
| 19 | The CNI (Container Network Interface) project consists of a |
| 20 | specification and libraries for writing plugins to configure network |
| 21 | interfaces in Linux containers, along with a number of supported |
| 22 | plugins. CNI concerns itself only with network connectivity of |
| 23 | containers and removing allocated resources when the container is |
| 24 | deleted. |
| 25 | |
| 26 | %prep |
| 27 | %setup -q -n plugins-%{version} |
| 28 | |
| 29 | %build |
| 30 | ./build_linux.sh |
| 31 | |
| 32 | %install |
| 33 | rm -rf $RPM_BUILD_ROOT |
| 34 | |
| 35 | install -d $RPM_BUILD_ROOT%{_sysconfdir}/cni/net.d |
| 36 | install -d $RPM_BUILD_ROOT%{_libexecdir}/cni |
| 37 | cp -p bin/* $RPM_BUILD_ROOT%{_libexecdir}/cni |
| 38 | |
| 39 | %clean |
| 40 | rm -rf $RPM_BUILD_ROOT |
| 41 | |
| 42 | %files |
| 43 | %defattr(644,root,root,755) |
| 44 | %doc CONTRIBUTING.md OWNERS.md README.md |
| 45 | %dir %{_sysconfdir}/cni |
| 46 | %dir %{_sysconfdir}/cni/net.d |
| 47 | %dir %{_libexecdir}/cni |
| 48 | %attr(755,root,root) %{_libexecdir}/cni/* |