2020-10-09 05:21:11 -04:00
|
|
|
|
%global _empty_manifest_terminate_build 0
|
2022-06-08 07:06:41 +00:00
|
|
|
|
Name: python-netifaces
|
|
|
|
|
|
Version: 0.11.0
|
|
|
|
|
|
Release: 1
|
|
|
|
|
|
Summary: Portable network interface information.
|
|
|
|
|
|
License: MIT
|
|
|
|
|
|
URL: https://github.com/al45tair/netifaces
|
|
|
|
|
|
Source0: https://files.pythonhosted.org/packages/a6/91/86a6eac449ddfae239e93ffc1918cf33fd9bab35c04d1e963b311e347a73/netifaces-0.11.0.tar.gz
|
2020-10-09 05:21:11 -04:00
|
|
|
|
|
|
|
|
|
|
%description
|
|
|
|
|
|
It’s been annoying me for some time that there’s no easy way to get the
|
|
|
|
|
|
address(es) of the machine’s network interfaces from Python. There is
|
|
|
|
|
|
a good reason for this difficulty, which is that it is virtually impossible
|
|
|
|
|
|
to do so in a portable manner. However, it seems to me that there should
|
|
|
|
|
|
be a package you can easy_install that will take care of working out the
|
|
|
|
|
|
details of doing so on the machine you’re using, then you can get on with
|
|
|
|
|
|
writing Python code without concerning yourself with the nitty gritty of
|
|
|
|
|
|
system-dependent low-level networking APIs.
|
|
|
|
|
|
This package attempts to solve that problem.
|
|
|
|
|
|
|
|
|
|
|
|
%package -n python3-netifaces
|
|
|
|
|
|
Summary: Portable network interface information.
|
|
|
|
|
|
Provides: python-netifaces
|
2022-06-08 07:06:41 +00:00
|
|
|
|
# Base build requires
|
2020-10-09 05:21:11 -04:00
|
|
|
|
BuildRequires: python3-devel
|
|
|
|
|
|
BuildRequires: python3-setuptools
|
2022-06-08 07:06:41 +00:00
|
|
|
|
BuildRequires: python3-pbr
|
|
|
|
|
|
BuildRequires: python3-pip
|
|
|
|
|
|
BuildRequires: python3-wheel
|
2020-10-09 05:21:11 -04:00
|
|
|
|
BuildRequires: python3-cffi
|
|
|
|
|
|
BuildRequires: gcc
|
|
|
|
|
|
%description -n python3-netifaces
|
|
|
|
|
|
It’s been annoying me for some time that there’s no easy way to get the
|
|
|
|
|
|
address(es) of the machine’s network interfaces from Python. There is
|
|
|
|
|
|
a good reason for this difficulty, which is that it is virtually impossible
|
|
|
|
|
|
to do so in a portable manner. However, it seems to me that there should
|
|
|
|
|
|
be a package you can easy_install that will take care of working out the
|
|
|
|
|
|
details of doing so on the machine you’re using, then you can get on with
|
|
|
|
|
|
writing Python code without concerning yourself with the nitty gritty of
|
|
|
|
|
|
system-dependent low-level networking APIs.
|
|
|
|
|
|
This package attempts to solve that problem.
|
|
|
|
|
|
|
|
|
|
|
|
%package help
|
|
|
|
|
|
Summary: Development documents and examples for netifaces
|
|
|
|
|
|
Provides: python3-netifaces-doc
|
|
|
|
|
|
%description help
|
|
|
|
|
|
It’s been annoying me for some time that there’s no easy way to get the
|
|
|
|
|
|
address(es) of the machine’s network interfaces from Python. There is
|
|
|
|
|
|
a good reason for this difficulty, which is that it is virtually impossible
|
|
|
|
|
|
to do so in a portable manner. However, it seems to me that there should
|
|
|
|
|
|
be a package you can easy_install that will take care of working out the
|
|
|
|
|
|
details of doing so on the machine you’re using, then you can get on with
|
|
|
|
|
|
writing Python code without concerning yourself with the nitty gritty of
|
|
|
|
|
|
system-dependent low-level networking APIs.
|
|
|
|
|
|
This package attempts to solve that problem.
|
|
|
|
|
|
|
|
|
|
|
|
%prep
|
2022-06-08 07:06:41 +00:00
|
|
|
|
%autosetup -n netifaces-%{version}
|
2020-10-09 05:21:11 -04:00
|
|
|
|
|
|
|
|
|
|
%build
|
|
|
|
|
|
%py3_build
|
|
|
|
|
|
|
|
|
|
|
|
%install
|
|
|
|
|
|
%py3_install
|
|
|
|
|
|
install -d -m755 %{buildroot}/%{_pkgdocdir}
|
|
|
|
|
|
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
|
|
|
|
|
|
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
|
|
|
|
|
|
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
|
|
|
|
|
|
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
|
|
|
|
|
|
pushd %{buildroot}
|
|
|
|
|
|
if [ -d usr/lib ]; then
|
2022-06-08 07:06:41 +00:00
|
|
|
|
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
|
2020-10-09 05:21:11 -04:00
|
|
|
|
fi
|
|
|
|
|
|
if [ -d usr/lib64 ]; then
|
2022-06-08 07:06:41 +00:00
|
|
|
|
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
|
2020-10-09 05:21:11 -04:00
|
|
|
|
fi
|
|
|
|
|
|
if [ -d usr/bin ]; then
|
2022-06-08 07:06:41 +00:00
|
|
|
|
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
|
2020-10-09 05:21:11 -04:00
|
|
|
|
fi
|
|
|
|
|
|
if [ -d usr/sbin ]; then
|
2022-06-08 07:06:41 +00:00
|
|
|
|
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
|
2020-10-09 05:21:11 -04:00
|
|
|
|
fi
|
|
|
|
|
|
touch doclist.lst
|
|
|
|
|
|
if [ -d usr/share/man ]; then
|
2022-06-08 07:06:41 +00:00
|
|
|
|
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
|
2020-10-09 05:21:11 -04:00
|
|
|
|
fi
|
|
|
|
|
|
popd
|
|
|
|
|
|
mv %{buildroot}/filelist.lst .
|
|
|
|
|
|
mv %{buildroot}/doclist.lst .
|
|
|
|
|
|
|
2022-06-08 07:06:41 +00:00
|
|
|
|
%check
|
|
|
|
|
|
%{__python3} setup.py test
|
|
|
|
|
|
|
2020-10-09 05:21:11 -04:00
|
|
|
|
%files -n python3-netifaces -f filelist.lst
|
|
|
|
|
|
%dir %{python3_sitearch}/*
|
|
|
|
|
|
|
|
|
|
|
|
%files help -f doclist.lst
|
|
|
|
|
|
%{_docdir}/*
|
|
|
|
|
|
|
|
|
|
|
|
%changelog
|
2022-06-08 07:06:41 +00:00
|
|
|
|
* Sat Jun 04 2022 OpenStack_SIG <openstack@openeuler.org> - 0.11.0-1
|
|
|
|
|
|
- Upgrade python3-netifaces to version 0.11.0
|
|
|
|
|
|
|
2021-08-04 21:18:47 +08:00
|
|
|
|
* Wed Aug 04 2021 chenyanpanHW <chenyanpan@huawei.com> - 0.10.9-2
|
|
|
|
|
|
- DESC: delete BuildRequires gdb
|
|
|
|
|
|
|
2020-10-09 05:21:11 -04:00
|
|
|
|
* Fri Oct 09 2020 Python_Bot <Python_Bot@openeuler.org>
|
|
|
|
|
|
- Package Spec generated
|
