Linux

Yeah agree on that, better be able to have freedom with a little downtime than have to put up with rules imposed by a corporation.

OK, back on track. xbps-src is not exactly like Portage. It's better, cuz you don't define anything when compiling. Basically, there's the template file that does everything regarding dependencies and packaging the application. You just run the script, tell it what you want to package that is in xbps-src and that's it. It chroots in wherever you cloned master from github, downloads all dependencies from the repo, downloads all compile binaries/libraries it might need and just goes to work. If a dependency is not in the repo, it takes it's xbps-src template, downloads the source and compiles that as well. The automation scrips are superb, there is practically very little that can go wrong during compile time. This is because not just anything can get as a template in xbps-src. It has to pass all build tests for all supported architectures before it's able to get in the source collection. That is why it's so stable, they don't leave anything to chance, they want clean tested packages. If you don't put in the work to correct your template, it's not getting into the source collection.