they have a wiki with insane nonsens about why they don't package certain things. Example:
pam
Package has different security-issues and is not oriented on the way of technical emancipation as Hyperbola is trying to adapt lightweight implementations.
Wait... they're militant enough about Free Software to refuse to package anything even slightly non-Free, but their "final goal" is to switch the kernel to BSD (i.e. away from copyleft)? WTF?
HyperbolaBSD is under a progressive migration by replacing all non GPL-compatible code. It will be replaced with new compatible code under Simplified BSD License. We do this in order to incorporate GPL code from other projects such as ReactOS, as well new code from scratch.
It's not clear to me that relicensing the existing code to GPL is what they're planning on doing; it sounds more like they're going to mix in GPL code but not change the existing files to GPL en masse after they finish harmonizing them to two-clause BSD.
Frankly, IMO that's too bad: I'd love to see them make the whole shebang GPLv3-or-later
Related question: is all Linux kernel code required to be licensed GPLv2-only, or are individual contributions allowed to be GPLv2-or-later? I'd be nice to see if that project (and stuff like HURD and ReactOS) could benefit from at least some Linux contributions, even if they can't copy it wholesale.
It's an ancient divide in parts of the FOSS community that believes copyleft licenses are not "free" because they force you to license contributions under the same license.
Yes, Hyperbola is very ideological and super strict, but it was always meant to be that way - to provide a system that works in some way and at the same time is as ethical and "clean" as possible. Some people value it over anything, and for them, Hyperbola is a good pick.