rpms/pyproject-rpm-macros
7
0
Fork 0
Code Issues Pull Requests Releases Activity
89c9b407fa
pyproject-rpm-macros/tests/python-flit-core.spec

55 lines
1.1 KiB
RPMSpec
Raw Normal View History

Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
Name: python-flit-core
Version: 3.0.0
Release: 0%{?dist}
Summary: Distribution-building parts of Flit
License: BSD
URL: https://pypi.org/project/flit-core/
Set %_pyproject_wheeldir and %_pyproject_builddir relative to the source tree, not $PWD This allows users to do: %build cd somewhere %pyproject_wheel cd - cd somewhere_else %pyproject_wheel cd - %install %pyproject_install Without a need to copy paste the wheels to a common location. This is in fact a breaking change, I'll make sure to adapt the affected packages in Fedora.
2021-05-27 13:16:16 +00:00
Source0: https://github.com/takluyver/flit/archive/%{version}/flit-%{version}.tar.gz
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
BuildArch: noarch
BuildRequires: python3-devel
BuildRequires: pyproject-rpm-macros
%description
Set %_pyproject_wheeldir and %_pyproject_builddir relative to the source tree, not $PWD This allows users to do: %build cd somewhere %pyproject_wheel cd - cd somewhere_else %pyproject_wheel cd - %install %pyproject_install Without a need to copy paste the wheels to a common location. This is in fact a breaking change, I'll make sure to adapt the affected packages in Fedora.
2021-05-27 13:16:16 +00:00
Test a wheel built from a subdirectory.
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
Test a build with pyproject.toml backend-path = .
flit-core builds with flit-core.
%package -n python3-flit-core
Summary: %{summary}
%description -n python3-flit-core
...
%prep
Set %_pyproject_wheeldir and %_pyproject_builddir relative to the source tree, not $PWD This allows users to do: %build cd somewhere %pyproject_wheel cd - cd somewhere_else %pyproject_wheel cd - %install %pyproject_install Without a need to copy paste the wheels to a common location. This is in fact a breaking change, I'll make sure to adapt the affected packages in Fedora.
2021-05-27 13:16:16 +00:00
%autosetup -p1 -n flit-%{version}
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
%generate_buildrequires
Set %_pyproject_wheeldir and %_pyproject_builddir relative to the source tree, not $PWD This allows users to do: %build cd somewhere %pyproject_wheel cd - cd somewhere_else %pyproject_wheel cd - %install %pyproject_install Without a need to copy paste the wheels to a common location. This is in fact a breaking change, I'll make sure to adapt the affected packages in Fedora.
2021-05-27 13:16:16 +00:00
cd flit_core
%pyproject_buildrequires: Make -r (include runtime) the default, use -R to opt-out See the proposal: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/2R6NKELTHAWE6PI3CCZBVW5PMGO5VPDG/ - -N now implies -R - the macro still guards against -Nr and now also against -Rr
2022-01-14 15:26:40 +00:00
# this runtime-requires pytoml which is no longer available in Fedora
%pyproject_buildrequires -R
Set %_pyproject_wheeldir and %_pyproject_builddir relative to the source tree, not $PWD This allows users to do: %build cd somewhere %pyproject_wheel cd - cd somewhere_else %pyproject_wheel cd - %install %pyproject_install Without a need to copy paste the wheels to a common location. This is in fact a breaking change, I'll make sure to adapt the affected packages in Fedora.
2021-05-27 13:16:16 +00:00
cd ..
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
%build
Set %_pyproject_wheeldir and %_pyproject_builddir relative to the source tree, not $PWD This allows users to do: %build cd somewhere %pyproject_wheel cd - cd somewhere_else %pyproject_wheel cd - %install %pyproject_install Without a need to copy paste the wheels to a common location. This is in fact a breaking change, I'll make sure to adapt the affected packages in Fedora.
2021-05-27 13:16:16 +00:00
cd flit_core
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
%pyproject_wheel
Set %_pyproject_wheeldir and %_pyproject_builddir relative to the source tree, not $PWD This allows users to do: %build cd somewhere %pyproject_wheel cd - cd somewhere_else %pyproject_wheel cd - %install %pyproject_install Without a need to copy paste the wheels to a common location. This is in fact a breaking change, I'll make sure to adapt the affected packages in Fedora.
2021-05-27 13:16:16 +00:00
cd ..
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
%install
%pyproject_install
Add the -l/-L flag to %pyproject_save_files - The -l flag can be used to assert at least 1 License-File was detected - The -L flag explicitly disables this check (which remains the default) Co-Authored-By: Maxwell G <maxwell@gtmx.me>
2023-09-27 12:37:15 +00:00
# there is no license file marked as License-File, hence not using -l
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
%pyproject_save_files flit_core
Add the -l/-L flag to %pyproject_save_files - The -l flag can be used to assert at least 1 License-File was detected - The -L flag explicitly disables this check (which remains the default) Co-Authored-By: Maxwell G <maxwell@gtmx.me>
2023-09-27 12:37:15 +00:00
%check
# internal check for our macros, we assume there is no license
grep -F %%license %{pyproject_files} && exit 1 || true
Support PEP 517 list based backend-path The PEP 517 shows an example backend-path like this: [build-system] # Defined by PEP 518: requires = ["flit"] # Defined by this PEP: build-backend = "local_backend" backend-path = ["backend"] https://www.python.org/dev/peps/pep-0517/#source-trees See that backend-path is a list. Our code previously only supported string path. Obviously a string path is wrong, but we keep it to support projects that have made the mistake, such as flit-core. Add a small integration test for both cases. Note that the new spec files deliberately don't do much, to save CI time.
2020-10-05 22:30:45 +00:00
%files -n python3-flit-core -f %{pyproject_files}
Reference in New Issue Copy Permalink