v8 client on rpm ?

[neilrieck]

Three days ago (so Aug-06, 2025) AlmaLinux announced (on reddit) support for prebuilt Nvidia drivers with CUDA support for both AlmaLinux-9 and AlmaLinux-10. I think this will change things for EL distros. Do you intend to now release a version of the 8.4 client for rpm-based systems?

BTW, until you do, I would think that you cannot retire the v7 client.

https://www.reddit.com/r/AlmaLinux/comm ... alinux_os/

https://almalinux.org/blog/2025-08-06-a ... ia-suport/

[muziqaz]

No,
pre-built deb only availability is hardware resource limitation. At least from dev side. Getting this up and running is "a bit" complicated

[Joe_H]

There are directions on the GitHub for Folding@home to create RPMs to install the client. However the developer currently does not have a development platform to create them. They do have platforms to compile the code and create installation packages for Windows, Debian based Linux and macOS.

[arisu]

I wonder why the developer needs a specific platform to do that. I've built RPMs on Debian-based machine. You don't need a RHEL-based system to package an RPM.

[calxalot]

You should discuss with marcos

[muziqaz]

I asked Joe if I can build all the packages, there was no answer to my question. I have all the platforms (Debian, fedora, oSuse, Endeavours). I successfully built packages for suse and fedora. If source files are in order I have no issues building the packages, however, as I said no reaction to my proposal. I did mention, that after I build the packages, they would still need to be validated and checked before published.

[arisu]

He could build the packages on the same server that he builds the cores on. He could have it build RPMs even if the system is Debian-based. Then there is no need to validate a third party compilation.

[calxalot]

I think the cores are built with github actions by others. Joseph then signs them before they are put on download servers.

[muziqaz]

He could build the packages on the same server that he builds the cores on. He could have it build RPMs even if the system is Debian-based. Then there is no need to validate a third party compilation.

I think time constraint is the issue here

[Marcos FRM]

Since I fixed and updated the tooling to make it possible to create the v8 RPM, it is possible to build the package from the sources. In theory, it would be possible, with rpmbuild available, to create it even within Debian and derivatives (requiring some changes here to avoid autodetection: https://github.com/CauldronDevelopmentL ... __.py#L126 ), but this is not something I test.

[muziqaz]

Marcos, I offered myself to build packages for all major distros, but there was no reaction to that in slack. I have no problem doing that, and I think it would be miles better, than expecting end user building packages for themselves.

[calxalot]

I believe you only need
‘package_type’ = ‘rpm’
In scons_options to defeat dist detection for building rpm on debian. Plus rpmbuild and whatever else is needed.

[calxalot]

But building rpm on debian 10 is probably not what you want for linking to support older redhat distributions.

[Marcos FRM]

But building rpm on debian 10 is probably not what you want for linking to support older redhat distributions.

Yeah, that's a good point, although the packages that determine the basic ABI have similar versions on Debian 10 and RHEL 8.

[PaulTV]

It's not that difficult to use containers to build for other distros. It's quick, clean and does not require running all those distros as servers. That would also be ideal in a build proces. I'm happy to share the dockerfile and script I have for rpm, however sloppy yhat script is