diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-inspektor.spec | 124 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 126 insertions, 0 deletions
@@ -0,0 +1 @@ +/inspektor-0.5.3.tar.gz diff --git a/python-inspektor.spec b/python-inspektor.spec new file mode 100644 index 0000000..0c0e8c4 --- /dev/null +++ b/python-inspektor.spec @@ -0,0 +1,124 @@ +%global _empty_manifest_terminate_build 0 +Name: python-inspektor +Version: 0.5.3 +Release: 1 +Summary: Inspektor python code checker and fixer +License: GNU General Public License v2 or later (GPLv2+) +URL: https://github.com/avocado-framework/inspektor +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/b5/e7/3a54e5b1f7bd978977e3ddd63325469d271bd103fd3e008d150d3a3c9f86/inspektor-0.5.3.tar.gz +BuildArch: noarch + +Requires: python3-six +Requires: python3-pycodestyle +Requires: python3-pylint +Requires: python3-cliff + +%description +Inspektor is a program used to verify the code of your python project. It +evolved from a set of scripts used to check patches and code of python projects +of the autotest organization [1]. As the project grew and new modules started +to be developed, we noticed the same scripts had to be copied to each new +project repo, creating a massive headache when we needed to update said +scripts. +Inspektor knows how to: +1) Check code with the help of `pylint`. +2) Check indentation of your code with the help of `pycodestyle`, + correcting it if you so deem appropriate. +3) Check whether your code is PEP8 compliant, correcting it if necessary + (only works if you have `autopep8` installed) if you so deem appropriate. +4) If your project is hosted on the autotest github area, it can apply pull + requests made against it, and check if it introduced any regression from + the metrics outlined above. +This all assumes you're working on a version control checkout of your code. +Currently inspektor knows how to handle subversion and git. + +%package -n python3-inspektor +Summary: Inspektor python code checker and fixer +Provides: python-inspektor +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-inspektor +Inspektor is a program used to verify the code of your python project. It +evolved from a set of scripts used to check patches and code of python projects +of the autotest organization [1]. As the project grew and new modules started +to be developed, we noticed the same scripts had to be copied to each new +project repo, creating a massive headache when we needed to update said +scripts. +Inspektor knows how to: +1) Check code with the help of `pylint`. +2) Check indentation of your code with the help of `pycodestyle`, + correcting it if you so deem appropriate. +3) Check whether your code is PEP8 compliant, correcting it if necessary + (only works if you have `autopep8` installed) if you so deem appropriate. +4) If your project is hosted on the autotest github area, it can apply pull + requests made against it, and check if it introduced any regression from + the metrics outlined above. +This all assumes you're working on a version control checkout of your code. +Currently inspektor knows how to handle subversion and git. + +%package help +Summary: Development documents and examples for inspektor +Provides: python3-inspektor-doc +%description help +Inspektor is a program used to verify the code of your python project. It +evolved from a set of scripts used to check patches and code of python projects +of the autotest organization [1]. As the project grew and new modules started +to be developed, we noticed the same scripts had to be copied to each new +project repo, creating a massive headache when we needed to update said +scripts. +Inspektor knows how to: +1) Check code with the help of `pylint`. +2) Check indentation of your code with the help of `pycodestyle`, + correcting it if you so deem appropriate. +3) Check whether your code is PEP8 compliant, correcting it if necessary + (only works if you have `autopep8` installed) if you so deem appropriate. +4) If your project is hosted on the autotest github area, it can apply pull + requests made against it, and check if it introduced any regression from + the metrics outlined above. +This all assumes you're working on a version control checkout of your code. +Currently inspektor knows how to handle subversion and git. + +%prep +%autosetup -n inspektor-0.5.3 + +%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 + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-inspektor -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Wed May 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.5.3-1 +- Package Spec generated @@ -0,0 +1 @@ +dca98ef469e609be3d9f707df01c80e2 inspektor-0.5.3.tar.gz |