Release version 1.0.0, first release candidate
Related: rhbz#1950291
This commit is contained in:
parent
71dcd3ad74
commit
127a259768
@ -4,10 +4,6 @@ pyproject RPM macros
|
||||
These macros allow projects that follow the Python [packaging specifications]
|
||||
to be packaged as RPMs.
|
||||
|
||||
They are still *provisional*: we can make non-backwards-compatible changes to
|
||||
the API.
|
||||
Please subscribe to Fedora's [python-devel list] if you use the macros.
|
||||
|
||||
They work for:
|
||||
|
||||
* traditional Setuptools-based projects that use the `setup.py` file,
|
||||
@ -17,7 +13,6 @@ They work for:
|
||||
These macros replace `%py3_build` and `%py3_install`, which only work with `setup.py`.
|
||||
|
||||
[packaging specifications]: https://packaging.python.org/specifications/
|
||||
[python-devel list]: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/
|
||||
|
||||
|
||||
Usage
|
||||
@ -332,11 +327,13 @@ Hence, the macro `%{pyproject_build_lib}` exists to be used like this:
|
||||
PYTHONPATH=%{pyproject_build_lib} ... build the docs here ...
|
||||
|
||||
This macro is currently **provisional** and the behavior might change.
|
||||
Please subscribe to Fedora's [python-devel list] if you use the macro.
|
||||
|
||||
The `%{pyproject_build_lib}` macro expands to an Shell `$(...)` expression and does not work when put into single quotes (`'`).
|
||||
|
||||
Depending on the pip version, the expanded value will differ:
|
||||
|
||||
[python-devel list]: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/
|
||||
|
||||
### New pip 21.3+ with in-tree-build (Fedora 36+)
|
||||
|
||||
|
@ -6,13 +6,14 @@ License: MIT
|
||||
# Specify --with tests to run the tests e.g. on EPEL
|
||||
%bcond_with tests
|
||||
|
||||
# Keep the version at zero and increment only release.
|
||||
# The release number indicates the feature set so only
|
||||
# increment it when syncing or rebasing from Fedora.
|
||||
# In other cases, such as backports, increment the point
|
||||
# release.
|
||||
Version: 0
|
||||
Release: 55%{?dist}
|
||||
# The idea is to follow the spirit of semver
|
||||
# Given version X.Y.Z:
|
||||
# Increment X and reset Y.Z when there is a *major* incompatibility
|
||||
# Increment Y and reset Z when new macros or features are added
|
||||
# Increment Z when this is a bugfix or a cosmetic change
|
||||
# Dropping support for EOL Fedoras is *not* considered a breaking change
|
||||
Version: 1.0.0~rc1
|
||||
Release: 1%{?dist}
|
||||
|
||||
# Macro files
|
||||
Source001: macros.pyproject
|
||||
@ -68,10 +69,6 @@ Requires: /usr/bin/sed
|
||||
These macros allow projects that follow the Python packaging specifications
|
||||
to be packaged as RPMs.
|
||||
|
||||
They are still provisional: we can make non-backwards-compatible changes to
|
||||
the API.
|
||||
Please subscribe to Fedora's python-devel list if you use the macros.
|
||||
|
||||
They work for:
|
||||
|
||||
* traditional Setuptools-based projects that use the setup.py file,
|
||||
@ -126,6 +123,9 @@ export HOSTNAME="rpmbuild" # to speedup tox in network-less mock, see rhbz#1856
|
||||
%license LICENSE
|
||||
|
||||
%changelog
|
||||
* Tue Jan 25 2022 Miro Hrončok <mhroncok@redhat.com> - 1.0.0~rc1-1
|
||||
- Release version 1.0.0, first release candidate
|
||||
|
||||
* Mon Jan 24 2022 Miro Hrončok <mhroncok@redhat.com> - 0-55
|
||||
- %%pyproject_buildrequires: Generate BuildRequires for this package
|
||||
This package is already installed, but this way, the resulting SRPM explicitly BuildRequires it
|
||||
|
Loading…
Reference in New Issue
Block a user