Re: python3.11-rpm to EPEL 9

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 15. 05. 23 16:49, Maxwell G wrote:
On Mon May 15, 2023 at 12:14 +0200, Miro Hrončok wrote:
Hello,

I'm working on adding python3.11-rpm to EPEL 9 and EPEL 9 Next.

See https://src.fedoraproject.org/rpms/python3-rpm/pull-request/3 and 4.

Cool!

I decided to reuse the python3-rpm component (currently epel7 only). Let me
know if I should not.

Are we able to build for multiple Python versions out of the same
specfile?

It's possible, but it's not nice.

In principle, this works:

  %build
  %define py3x_build() %{global python3_pkgversion %1}%py3_build
  %py3x_build 39
  %py3x_build 3.11

  %install
  %define py3x_install() %{global python3_pkgversion %1}%py3_install
  %py3x_install 39
  %py3x_install 3.11

But with a project like RPM, we might need to run configure multiple times as well and create separate working directories. Will need to check.

That PR has:

```
+ # We'll build python3.11-rpm only for now
+ # Once a new Python version is added,
+ # the spec will need to change to support multiple Pythons anyway
+ %global python3_pkgversion 3.11
```

but I thought we got rid of the %py3_other_* stuff that allowed building
for multiple Python versions out of the same specfile.

We did.

Unless there's some other way to work around this, I'd use a
python3.11-rpm or python3.11-rpm-epel component like we've been doing
for the other alt python stacks in RHEL 8.

I consider the "not nice" way easier, as it will only require to keep one package synced with c8s rpm, and not many. Will try to hack it up and show how it looks like.

If there is a significant demand, I can try add this (and python39-rpm) to EPEL
8 as well.

As I said on IRC, I'd like that for fedrq.

Ack.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux