Epoch: 3 %define pypi_name py2pack %define python_name python3-%{pypi_name} Name: python-%{pypi_name} Version: 1.3.0 Release: %autorelease # Fill in the actual package summary to submit package to Fedora Summary: Generate distribution packages from PyPI # Check if the automatically generated License and its spelling is correct for Fedora # https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/ License: Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. (FIXME:No SPDX) URL: http://github.com/huakim/py2pack Source: py2pack-%{version}.tar.gz BuildRequires: pyproject-rpm-macros BuildRequires: python3-devel BuildRequires: fdupes BuildArch: noarch # Fill in the actual package description to submit package to Fedora %global _description %{expand: Py2pack: Generate distribution packages from PyPI ================================================= .. image:: https://github.com/openSUSE/py2pack/actions/workflows/tox.yml/badge.svg :target: https://github.com/openSUSE/py2pack/actions/workflows/tox.yml :alt: Unit tests This script allows to generate RPM spec or DEB dsc files from Python modules. It allows to list Python modules or search for them on the Python Package Index (PyPI). Conveniently, it can fetch tarballs and changelogs making it an universal tool to package Python modules. Installation ------------ To install py2pack from the `Python Package Index`_, simply: .. code-block:: bash $ python3 -mpip install py2pack You can also check your distro of choice if they provide packages. For openSUSE Tumbleweed and Leap 15.X, you can .. code-block:: bash $ sudo zypper install python3-py2pack Usage ----- Lets suppose you want to package zope.interface_ and you don't know how it is named exactly. First of all, you can search for it and download the source tarball if you found the correct module: .. code-block:: bash $ py2pack search zope.interface searching for module zope.interface... found zope.interface-3.6.1 $ py2pack fetch zope.interface downloading package zope.interface-3.6.1... from http://pypi.python.org/packages/source/z/zope.interface/zope.interface-3.6.1.tar.gz As a next step you may want to generate a package recipe for your distribution. For RPM_-based distributions (let's use openSUSE_ as an example), you want to generate a spec file (named 'python-zope.interface.spec'): .. code-block:: bash $ py2pack generate zope.interface -t opensuse.spec -f python-zope.interface.spec The source tarball and the package recipe is all you need to generate the RPM_ (or DEB_) file. This final step may depend on which distribution you use. Again, for openSUSE_ (and by using the `Open Build Service`_), the complete recipe is: .. code-block:: bash $ osc mkpac python-zope.interface $ cd python-zope.interface $ py2pack fetch zope.interface $ py2pack generate zope.interface -f python-zope.interface.spec $ osc build ... Depending on the module, you may have to adapt the resulting spec file slightly. To get further help about py2pack usage, issue the following command: .. code-block:: bash $ py2pack help Hacking and contributing ------------------------ You can test py2pack from your git checkout by executing the py2pack module. Edit `py2pack/version.py` file changing the version number. Adding +1 to the revision number and optionally appending .dev1 is enough and makes sure that you can distinguish your hackish version from an installed one. From the py2pack directory, install the py2pack module locally. .. code-block:: bash $ pip install -e . Now you can run your hackish py2pack version. It is usually located in $HOME/.local/bin/py2pack .. code-block:: bash $ py2pack Fork `the repository`_ on Github to start making your changes to the **master** branch (or branch off of it). Don't forget to write a test for fixed issues or implemented features whenever appropriate. You can invoke the testsuite from the repository root directory via `tox`_: .. code-block:: bash $ tox To run a single test class via `tox`_, use i.e.: .. code-block:: bash $ tox -epy38 test.test_py2pack:Py2packTestCase You can also run `pytest`_ directly: .. code-block:: bash $ pytest It assumes you have the test dependencies installed (available on PYTHONPATH) on your system. :copyright: (c) 2013 Sascha Peilicke. :license: Apache-2.0, see LICENSE for more details. .. _argparse: http://pypi.python.org/pypi/argparse .. _Jinja2: http://pypi.python.org/pypi/Jinja2 .. _zope.interface: http://pypi.python.org/pypi/zope.interface/ .. _openSUSE: http://www.opensuse.org/en/ .. _RPM: http://en.wikipedia.org/wiki/RPM_Package_Manager .. _DEB: http://en.wikipedia.org/wiki/Deb_(file_format) .. _`Python Package Index`: https://pypi.org/ .. _`Open Build Service`: https://build.opensuse.org/package/show/devel:languages:python/python-py2pack .. _`the repository`: https://github.com/openSUSE/py2pack .. _`pytest`: https://github.com/pytest-dev/pytest .. _`tox`: http://testrun.org/tox } %description %_description %package -n %{python_name} Requires: py2pack-base-templates Summary: %{summary} %description -n %{python_name} %_description %prep %autosetup -p1 -n %{pypi_name}-%{version} %generate_buildrequires # Keep only those extras which you actually want to package or use during tests %pyproject_buildrequires %build %pyproject_wheel %install mkdir -pv %{buildroot}%{_datadir}/py2pack/templates cp py2pack/templates/* %{buildroot}%{_datadir}/py2pack/templates %pyproject_install # For official Fedora packages, including files with '*' +auto is not allowed # Replace it with a list of relevant Python modules/globs and list extra files in %%files %pyproject_save_files '*' +auto %files -n %{python_name} -f %{pyproject_files} %changelog %autochangelog %package -n py2pack-base-templates Summary: base templates %description -n py2pack-base-templates base templates. %files -n py2pack-base-templates %dir %{_datadir}/py2pack %dir %{_datadir}/py2pack/templates %{_datadir}/py2pack/templates/*