Fedora 36 as a Slackware 15 (stable) 3rd party repo ...

Post#1 by **fu11m00n** » 02 May 2026, 01:19

Salutations...

The following instructions are for selecting and converting Fedora 36 packages to Slackware 15 (stable) packages...

Go to pkgs.org.
Go to "filter" deselect "all".
Then select Fedora 43.
Then enter your package in "search".
Then select your package.
Go to "links" and copy the package homepage
Then copy... paste and go in your browser.
Select "builds".

Choose the Fedora 36 .rpm (it's compatible with Slackware 15 stable) preferably...
the 01/22 release (if available) otherwise the one closest to 02/22.

Download and "convert" to .xzm

Enjoy.

Pls Note: You may need to install upstream or 3rd party dependences to support the converted packages.

Post#2 by **Ed_P** » 02 May 2026, 05:37

Dupe posting. <Solved?>...Fedora 36 as a Slackware 15 (stable) 3rd party repo ... (Post by fu11m00n #105339)

Post#3 by **fu11m00n** » 02 May 2026, 09:58

@ Ed_P... thanks.

It's been a long time.
I am maintainer of a Sourceforge project listed on DistroWatch that Patrick Volkerding (BDFL) himself is following (and mentoring).

Dupe posting? You are correct. And you know what to do.
If you don't... I encourage you to PM me. We have spoken in the past. I believe we can sort things out.

Check out my thread @ "Porteus Haters".

Post#4 by **fu11m00n** » 02 May 2026, 10:36

Salutations all...

The purpose of this thread is to shed light on the the fact that Slackware
from it's earliest days was never meant to be a 3rd party repo.

And this makes sense because a repository out the box should always be based on "use case".
Just like Debian and Fedora... Slackware @ it's core is general purpose.

It's "use case" is not to address edge cases and outliers.
But some... would say, "then why not use a 3rd party repo like SlackDCE"?

That makes sense too but you could also benefit... from the additional packages from Fedora's vast library.

In any case... SlackDCE does not support Aarch64. And the Debian repo can only be converted to x86_64 (Aarch is experimental).
And Stuart Winter's Slackware (ARM) is a clone of Slackware upstream so it does not support 3rd party.

In addition... Aarch64 is an issue if you want to customize Stuart's creation to create an ARM version of Porteus.

So what to do? Well... I'm glad you asked.
If the goal is to convert to Slackware 15 "stable" (circa 02/22) then that requires Fedora 36 (circa 01/22) to avoid libc incompatibility.

Pkgs.org is golden. It's one of the best ways to acquire .rpm and .deb 3rd party packages.
The key however... it to match parity. The package version (also year and month) is very important.

Post#5 by **fu11m00n** » 03 May 2026, 21:18

Update... now even better!

The same procedure works with OpenMandriva 4.2 (also quite compatible with Slackware 15 "stable").
The immediate benefit is that all packages are built with... Musl/Clang instead of Glibc/GCC ("circular hell").

https://abf-downloads.openmandriva.org/ ... n/release/
https://abf-downloads.openmandriva.org/ ... d/release/

https://abf-downloads.openmandriva.org/ ... n/release/
https://abf-downloads.openmandriva.org/ ... d/release/

Caveat: In some cases the symlink directory paths for the OpenMandriva .rpm's
do not match Slackware .txz's so make sure your /etc/environment PATH variable is (@ least)...
PATH=/usr/bin:/usr/lib64:/usr/sbin:/bin:/etc:/lib64:/opt:/sbin:/tmp:/var

Pls Note: Always remember the "golden" rule... test before you ship!