From e7ad9fa67dcdee1f1efb370d47c841c8eb0d4b62 Mon Sep 17 00:00:00 2001 From: CoprDistGit Date: Mon, 10 Apr 2023 13:57:21 +0000 Subject: automatic import of python-cement --- python-cement.spec | 261 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 261 insertions(+) create mode 100644 python-cement.spec (limited to 'python-cement.spec') diff --git a/python-cement.spec b/python-cement.spec new file mode 100644 index 0000000..5faf3ac --- /dev/null +++ b/python-cement.spec @@ -0,0 +1,261 @@ +%global _empty_manifest_terminate_build 0 +Name: python-cement +Version: 3.0.8 +Release: 1 +Summary: Application Framework for Python +License: BSD +URL: https://builtoncement.com +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/be/c3/69d35ecc69a69801d7dad88c8943cf7f82b28b92ea9c2352ca6ca0f9e9cf/cement-3.0.8.tar.gz +BuildArch: noarch + +Requires: python3-colorlog +Requires: python3-pyYaml +Requires: python3-jinja2 +Requires: python3-pylibmc +Requires: python3-pystache +Requires: python3-redis +Requires: python3-tabulate +Requires: python3-watchdog +Requires: python3-pyYaml + +%description +cement_cement-py35_1 /bin/bash Up +cement_cement-py36_1 /bin/bash Up +cement_cement-py37_1 /bin/bash Up +cement_cement-py38_1 /bin/bash Up +cement_cement-py39_1 /bin/bash Up +cement_cement_1 /bin/bash Up +cement_memcached_1 docker-entrypoint.sh memcached Up 11211/tcp +cement_redis_1 docker-entrypoint.sh redis ... Up 6379/tcp +$ docker-compose exec cement-py37 /bin/bash +|> cement-py37 <| src # +``` +### VirtualENV +An traditional VirtualENV helper is available: +``` +$ make virtualenv +$ source env/bin/activate +|> cement <| $ +``` +### Vagrant +An alternative option is included to run Vagrant for development. This is partially supported, primarily for the purpose of developing/testing on Windows as well as testing specific issues on target operating systems. +To see a list of configured systems: +``` +$ vagrant status +``` +#### Linux +``` +$ vagrant up linux +$ vagrant ssh linux +vagrant@linux $ cd /vagrant +vagrant@linux $ bash scripts/vagrant/bootstrap.sh +vagrant@linux $ make virtualenv +vagrant@linux $ source env/bin/activate +|> cement >| $ +``` +#### Windows +*Windows development and support is not 100% complete. Cement is known to run and work on Windows, however it is not a primary target for development and as such the setup is not as streamlined and currently has several known errors.* +The following assumes you're running these two initial commands from a unix based system: +``` +$ make clean +$ vagrant up windows +``` +RDP or Login to Desktop/Console, and open a PowerShell terminal: +``` +C:\> cd C:\Vagrant +C:\Vagrant> powershell.exe scripts\vagrant\bootstrap.ps1 +C:\Vagrant> make virtualenv-windows +C:\Vagrant> .\env-windows\Scripts\activate.ps1 +C:\Vagrant> make test-core +``` +*Note that only the core library is fully tested on Windows.* +### Running Tests and Compliance +Cement has a strict policy that all code and tests meet PEP8 guidelines, therefore `flake8` is called before any unit tests run. All code submissions require 100% test coverage and PEP8 compliance: +Execute the following to run all compliance and unit tests: +``` +$ make test +``` +A coverage report is printed to console, as well as the HTML version created in `coverage-report`: +``` +$ open coverage-report/index.html +``` +See `Makefile` for all other common development actions. + +%package -n python3-cement +Summary: Application Framework for Python +Provides: python-cement +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-cement +cement_cement-py35_1 /bin/bash Up +cement_cement-py36_1 /bin/bash Up +cement_cement-py37_1 /bin/bash Up +cement_cement-py38_1 /bin/bash Up +cement_cement-py39_1 /bin/bash Up +cement_cement_1 /bin/bash Up +cement_memcached_1 docker-entrypoint.sh memcached Up 11211/tcp +cement_redis_1 docker-entrypoint.sh redis ... Up 6379/tcp +$ docker-compose exec cement-py37 /bin/bash +|> cement-py37 <| src # +``` +### VirtualENV +An traditional VirtualENV helper is available: +``` +$ make virtualenv +$ source env/bin/activate +|> cement <| $ +``` +### Vagrant +An alternative option is included to run Vagrant for development. This is partially supported, primarily for the purpose of developing/testing on Windows as well as testing specific issues on target operating systems. +To see a list of configured systems: +``` +$ vagrant status +``` +#### Linux +``` +$ vagrant up linux +$ vagrant ssh linux +vagrant@linux $ cd /vagrant +vagrant@linux $ bash scripts/vagrant/bootstrap.sh +vagrant@linux $ make virtualenv +vagrant@linux $ source env/bin/activate +|> cement >| $ +``` +#### Windows +*Windows development and support is not 100% complete. Cement is known to run and work on Windows, however it is not a primary target for development and as such the setup is not as streamlined and currently has several known errors.* +The following assumes you're running these two initial commands from a unix based system: +``` +$ make clean +$ vagrant up windows +``` +RDP or Login to Desktop/Console, and open a PowerShell terminal: +``` +C:\> cd C:\Vagrant +C:\Vagrant> powershell.exe scripts\vagrant\bootstrap.ps1 +C:\Vagrant> make virtualenv-windows +C:\Vagrant> .\env-windows\Scripts\activate.ps1 +C:\Vagrant> make test-core +``` +*Note that only the core library is fully tested on Windows.* +### Running Tests and Compliance +Cement has a strict policy that all code and tests meet PEP8 guidelines, therefore `flake8` is called before any unit tests run. All code submissions require 100% test coverage and PEP8 compliance: +Execute the following to run all compliance and unit tests: +``` +$ make test +``` +A coverage report is printed to console, as well as the HTML version created in `coverage-report`: +``` +$ open coverage-report/index.html +``` +See `Makefile` for all other common development actions. + +%package help +Summary: Development documents and examples for cement +Provides: python3-cement-doc +%description help +cement_cement-py35_1 /bin/bash Up +cement_cement-py36_1 /bin/bash Up +cement_cement-py37_1 /bin/bash Up +cement_cement-py38_1 /bin/bash Up +cement_cement-py39_1 /bin/bash Up +cement_cement_1 /bin/bash Up +cement_memcached_1 docker-entrypoint.sh memcached Up 11211/tcp +cement_redis_1 docker-entrypoint.sh redis ... Up 6379/tcp +$ docker-compose exec cement-py37 /bin/bash +|> cement-py37 <| src # +``` +### VirtualENV +An traditional VirtualENV helper is available: +``` +$ make virtualenv +$ source env/bin/activate +|> cement <| $ +``` +### Vagrant +An alternative option is included to run Vagrant for development. This is partially supported, primarily for the purpose of developing/testing on Windows as well as testing specific issues on target operating systems. +To see a list of configured systems: +``` +$ vagrant status +``` +#### Linux +``` +$ vagrant up linux +$ vagrant ssh linux +vagrant@linux $ cd /vagrant +vagrant@linux $ bash scripts/vagrant/bootstrap.sh +vagrant@linux $ make virtualenv +vagrant@linux $ source env/bin/activate +|> cement >| $ +``` +#### Windows +*Windows development and support is not 100% complete. Cement is known to run and work on Windows, however it is not a primary target for development and as such the setup is not as streamlined and currently has several known errors.* +The following assumes you're running these two initial commands from a unix based system: +``` +$ make clean +$ vagrant up windows +``` +RDP or Login to Desktop/Console, and open a PowerShell terminal: +``` +C:\> cd C:\Vagrant +C:\Vagrant> powershell.exe scripts\vagrant\bootstrap.ps1 +C:\Vagrant> make virtualenv-windows +C:\Vagrant> .\env-windows\Scripts\activate.ps1 +C:\Vagrant> make test-core +``` +*Note that only the core library is fully tested on Windows.* +### Running Tests and Compliance +Cement has a strict policy that all code and tests meet PEP8 guidelines, therefore `flake8` is called before any unit tests run. All code submissions require 100% test coverage and PEP8 compliance: +Execute the following to run all compliance and unit tests: +``` +$ make test +``` +A coverage report is printed to console, as well as the HTML version created in `coverage-report`: +``` +$ open coverage-report/index.html +``` +See `Makefile` for all other common development actions. + +%prep +%autosetup -n cement-3.0.8 + +%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-cement -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Mon Apr 10 2023 Python_Bot - 3.0.8-1 +- Package Spec generated -- cgit v1.2.3