## START: Set by rpmautospec ## (rpmautospec version 0.7.3) ## RPMAUTOSPEC: autorelease, autochangelog %define autorelease(e:s:pb:n) %{?-p:0.}%{lua: release_number = 2; base_release_number = tonumber(rpm.expand("%{?-b*}%{!?-b:1}")); print(release_number + base_release_number - 1); }%{?-e:.%{-e*}}%{?-s:.%{-s*}}%{!?-n:%{?dist}} ## END: Set by rpmautospec # Generated by rust2rpm 26 %bcond_without check %global crate python-launcher Name: rust-python-launcher Version: 1.0.1 Release: %autorelease Summary: Python launcher for Unix License: MIT URL: https://crates.io/crates/python-launcher Source: %{crates_source} # Manually created patch for downstream crate metadata changes # * drop unused, benchmark-only criterion dev-dependency Patch: python-launcher-fix-metadata.diff BuildRequires: cargo-rpm-macros >= 24 %global _description %{expand: The Python Launcher for Unix. Launch your Python interpreter the lazy/smart way! This launcher is an implementation of the py command for Unix-based platforms. The goal is to have py become the cross-platform command that Python users typically use to launch an interpreter while doing development. By having a command that is version-agnostic when it comes to Python, it side-steps the "what should the python command point to?" debate by clearly specifying that upfront (i.e. the newest version of Python that can be found). This also unifies the suggested command to document for launching Python on both Windows as Unix as py has existed as the preferred command on Windows since 2012 with the release of Python 3.3. Typical usage would be: py -m venv .venv py ... # Whatever you would normally use `python` for during development. This creates a virtual environment in a .venv directory using the latest version of Python installed. Subsequent uses of py will then use that virtual environment as long as it is in the current (or higher) directory; no environment activation required (although the Python Launcher supports activated environments as well)! A non-goal of this launcher is to become the way to launch the Python interpreter all the time. If you know the exact interpreter you want to launch then you should launch it directly; same goes for when you have requirements on the type of interpreter you want. The Python Launcher should be viewed as a tool of convenience, not necessity.} %description %{_description} %package -n %{crate} Summary: %{summary} # 0BSD OR MIT OR Apache-2.0 # Apache-2.0 # Apache-2.0 OR MIT # MIT # MIT OR Apache-2.0 # MIT OR Zlib OR Apache-2.0 # Unlicense OR MIT License: MIT AND Apache-2.0 AND (0BSD OR MIT OR Apache-2.0) AND (Apache-2.0 OR MIT) AND (MIT OR Zlib OR Apache-2.0) AND (Unlicense OR MIT) Provides: py = %{?epoch:%{epoch}:}%{version}-%{release} Provides: py%{?_isa} = %{?epoch:%{epoch}:}%{version}-%{release} # LICENSE.dependencies contains a full license breakdown %description -n %{crate} %{_description} %files -n %{crate} %license LICENSE %license LICENSE.dependencies %doc CHANGELOG.md %doc README.md %{_bindir}/py %{_mandir}/man1/py.1.* %{fish_completions_dir}/py.fish %package devel Summary: %{summary} BuildArch: noarch %description devel %{_description} This package contains library source intended for building other packages which use the "%{crate}" crate. %files devel %license %{crate_instdir}/LICENSE %doc %{crate_instdir}/CHANGELOG.md %doc %{crate_instdir}/README.md %{crate_instdir}/ %package -n %{name}+default-devel Summary: %{summary} BuildArch: noarch %description -n %{name}+default-devel %{_description} This package contains library source intended for building other packages which use the "default" feature of the "%{crate}" crate. %files -n %{name}+default-devel %ghost %{crate_instdir}/Cargo.toml %prep %autosetup -n %{crate}-%{version} -p1 %cargo_prep %generate_buildrequires %cargo_generate_buildrequires %build %cargo_build %{cargo_license_summary} %{cargo_license} > LICENSE.dependencies %install %cargo_install # install man page mkdir -p %{buildroot}/%{_mandir}/man1 cp -pav man-page/py.1 %{buildroot}/%{_mandir}/man1/ # install fish completions mkdir -p %{buildroot}/%{fish_completions_dir} cp -pav completions/py.fish %{buildroot}/%{fish_completions_dir}/ %if %{with check} %check %cargo_test %endif %changelog ## START: Generated by rpmautospec * Sat Jul 20 2024 Fedora Release Engineering - 1.0.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild * Sun Jul 07 2024 Fabio Valentini - 1.0.1-1 - Update to version 1.0.1; Fixes RHBZ#2295557 * Thu May 23 2024 Fabio Valentini - 1.0.0-12 - Rebuild with Rust 1.78 to fix incomplete debuginfo and backtraces * Fri Jan 26 2024 Fedora Release Engineering - 1.0.0-11 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild * Sat Aug 05 2023 Fabio Valentini - 1.0.0-10 - Regenerate with rust2rpm v24 * Fri Jul 21 2023 Fedora Release Engineering - 1.0.0-9 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Sat Feb 04 2023 Fabio Valentini - 1.0.0-8 - Rebuild for fixed frame pointer compiler flags in Rust RPM macros * Sat Jan 21 2023 Fedora Release Engineering - 1.0.0-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Sat Jul 23 2022 Fedora Release Engineering - 1.0.0-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Tue Feb 15 2022 Zbigniew Jędrzejewski-Szmek - 1.0.0-5 - Rebuild with package notes * Tue Jan 25 2022 Fabio Valentini - 1.0.0-4 - Rebuild with thread_local 1.1.4 for RUSTSEC-2022-0006 * Fri Jan 21 2022 Fedora Release Engineering - 1.0.0-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Sun Nov 14 2021 Robert-André Mauchin - 1.0.0-2 - Bump assert_cmd to 2.0.0 * Fri Sep 03 2021 Fabio Valentini - 1.0.0-1 - Initial import (#2000931) ## END: Generated by rpmautospec