0x4E4F

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.

Lol, that's normal in Arch, Void, Gentoo, LFS.

Almost every proprietery software there is out there has only Debian/Ubuntu packages, yet we run them in Arch, Void, Gentoo... as long as the dependencies are there, it doesn't matter what distro you run the software on.

Repackaging is easy though with xbps-src.

Void runs even faster, I've tried (on an older RPi, but still).

Some patches are there for software that reauires systemd or parts of it.

Not just musl, software that depends on systemd (or parts of it) as well.

We also need to patch binaries as well sometimes 😁. It is fun though, cutter and/or iaito are great tools.