0x4E4F

Yes, that should be possible.

But, I would first try the naked Void install with additional firmware. lspci and lsusb should point you to which manufaturer you're missing drivers for and you can install the additional firmware from the non-free Void repo, (you can add that manually to the repos, it doesn't come bundled with it). If that deosn't work, hey, you can always try repackaging 🤷. Just remember to remove the non-free firmware first, so it doesn't conict with the repackaged stuff from RH (yes, things like firmware packages or drivers can conflict with each other, especially since you're taking them from a repo xbps knows nothing about).

Yeah, just test it out on old x86 hardware, that's what I did at first as well.

IDK, depends on the CPU architecture... I'm not that famlilar with Macs, but if it's x64 capable, yeah, no problem.

I think there was a list of supported architectures on the website 🤔...

Can't find it now. Anyway, x86, x86_64, ARMv6/v7/v8 are all supported out of the box. PPC is also supported, but you have to build everything yourself from scratch (there was one maintainer that maintained a PPC build, but he gave up on it a year or so ago, he went on to form Chimera Linux), which can be done by crossbuilding on any of the supported architectures using xbps-src... but that's a lot of work to be honest, if it's a PPC architecture, you're better off using Chimera Linux.

I do recommend trying the glibc version first, since you'd have to run everything that depends on glibc in a chroot, on a musl install. Yeah, it is doable, but if you're not really experienced with this, just use the glibc version.

No Void 😔.

I think you'll like it 😊.

You must be running hardware not older than 4 or 5 years. Try running it on hardware 10+ years old.

I'm also a fan of centralized places to handle things (I prefer having just one package manager, not the package manager and flatpak and pip and god knows what else), but there are other init/service managers.

How does xbps-src handle dependencies?

Regarding feeding it rpm/deb packages, it reads the dependencies from the deb/rpm package and uses the equvalent names in shlibs (shared libraries). That's basically a list of libs that some applications expect to find, so xbps-src just makes a symbolic link to the equvalent lib with the name that the app expects to find. Look at the example I gave above with libtiff.

Regarding everything else built from source, there are 3 types of dependencies, since the packages are built in a chroot: hostdepends - dependcies that are requires by the chroot system, makedepends - dependencies that are required to build the package, depends - dependencies that are required to run the package. The ones that are required just to run the thing are the just depends, the other 2 are required for building only.

What happens if a dependency is not available in the Void repos?

You find the equivalent lib in Void (the xtools package is a great help for a lot of things, including repackaging), add it to shlibs and that's it. If it's proprietery or Void doesn't have it (higly unlikely if it's open source... I have yest to run in a case like that), you have to put in the template as a distfile (if proprietery and only binary versions are available), or you have to compile from source (also done automatically by xbps-src once it detect there are distfiles for the lib and is not present in the repos).

Building from source is also easy in most cases (when no patches need to be applied). xbps-src has build styles (gnu-make, meson, etc.), so you just define that in the buildstyle parameter and it does everything automatically, including adding missing build dependencies.

xbps-src goes through a lot of trouble to make packaging and building as automatic as possible.

Meeh, it was funny... not a meme per say, but still, funny 😁.

Closing handles on services that for god knows what reason, just hang. Also stopping and starting services again doesn't always work as intended.

No, just bootup and general responsivness of the system. Software is still compiled by the ssme compilers used in other distros. Everything is not magically faster.

Though on the musl build, yeah, it is faster. Trouble is, you can't run glibc software on it. Through chroot, yeah, but natively, no.

OK, I have to admit, i kinda fell for it 😂.

The syntax is a bit different, but everything else, more or less the same. In fact, if you just wanna repackage a deb or an rpm, it's even easier than in Arch, xbps-src can handle deb and rpm automatically, it detects dependencies and does repackaging on it's own. You basically just have to feed it the deb/rpm file in a one liner, that's it.

I should probably give an example. Here is the template file (they're called templates in Void) for Viber. You basically just feed it the deb, do a vcopy (copy operation specific to xbps-src) and that's it, everything else regarding the repackaging is done automatically by xbps-src.