This is an old revision of the document!
Incompatible Packages and Projects
As project oriented on free, permissive licensed software Hyperbola has a strict way to integrate different maintained software. Followed up the possible reasonings for us to decline packages for building or remove them from our repositories:
- Package (software) is only available for the GNU/Linux-platform itself and is not as port for BSD, including the exclusive usage of interfaces being only available on GNU/Linux
- Package (software) is bloated in technical, social and / or ecological aspects, which means integration makes it the one major dependency for many others or its own dependency-tree is way more complex
- Package (software) includes several already known vulnerable and insecure implementations and also opposes the essential long-term support from Hyperbola as the maintaining person(s) just state to always update to the newest version without having any interest in stable release-schedules
- Package (software) is semi- or non-free in its outcome and includes several parts impossible to remove or to modify, also declining the modification without asking
- Package (software) is in its original state not complete free and libre, therefore patching would be needed but this would end in such tremendous work that even forking would be the better option
- Package (software) is not based on the pure work of the community and is just a corporate project pretending to be free and libre in its licensing with people attend but nevertheless misusing their engagement so named copyright-holding companies get their profit with
All of those named points are reducing or even worse declining the elemental freedom of the user, to learn, to modify, to share and to use for any purpose without restrictions. Hyperbola was and is always about essential freedom and with its goal of technical emancipation oriented on lightweight software and design so people can learn and fully control their system by all means. Including software-projects and packages based on them opposing this will never be done!
List of packages and projects being not integrated and removed
| Name | Description | Reasoning |
|---|---|---|
| systemd | system and service manager | See our reasoning here. |
| dbus | Freedesktop.org message bus system | See our reasoning here. |
| openssl | Toolkit for Secure Sockets Layer and Transport Layer Security | See our reasoning here. |
| bluez | Daemons for the bluetooth protocol stack | See our reasoning here. |
| xorg | Xorg X server | See our reasoning here. |
| gtk-doc | Documentation tool for public library API | There is no need to implement a toolset for generating any kind of HTML-based documentation or even more complex file-formats while man pages are absolutely sufficient. |
| libcanberra | Implementation of the XDG Sound Theme Specification | Package is not needed for running any kind of application and just make more work to maintain it, while the software itself is using more in its own dependency-tree. |
| avahi | Service Discovery using mDNS/DNS-SD | Package is named as being compatible with the non-free framework Bonjour from Apple and is also a possible attack-vector throughout the network. |
| zstd | Zstandard - Fast real-time compression algorithm | Package is free and permissive licensed but nevertheless bloat within especially social and ecological aspects as some projects implement it as mandatory depedency without any kind of choice left to fast select another interface and depedency. Also an example of corporate projects pretending to be free and libre! |
| protobuf | Protocol Buffers - data interchange format | Package is free and permissive licensed but nevertheless bloat within especially social and ecological aspects as some projects implement it as mandatory depedency without any kind of choice left to fast select another interface and depedency. Also an example of corporate projects pretending to be free and libre! |
| libatasmart | ATA S.M.A.R.T. Reading and Parsing Library | Package is based on interfaces only available on GNU/Linux, making it impossible to be ported and / or used further. |
| java / openjdk | Java development kit | See our reasoning here. |
| rust | Systems programming language | See our reasoning here. |
| sudo | Give certain users the ability to run some commands as root | See our reasoning here. |
| gettext | GNU internationalization library | Enforcing usage of Java and CSharp (.Net), while including references towards those non-free language implementations. Package itself is completely bloated in all named categories. |
| mono | Implementation of the .NET platform including runtime and compiler | Package is free and permissive licensed but nevertheless bloat within especially social and ecological aspects as some projects implement it as mandatory depedency without any kind of choice left to fast select another interface and depedency. Also an example of corporate projects pretending to be free and libre as the company Microsoft has only given the permission for the core-parts, holding back essential copyright material. |
| nodejs | Evented I/O for V8 javascript | Package is free and permissive licensed on the first look but nevertheless bloat within all parts. Also it is a possible attack-vector as JavaScript is exectued at run- and build-time with many further needed dependencies for projects. Further reasoning is to be read here. |
| npm | A package manager for javascript | We do not distribute any further package-manager outside our own as there will be never any kind of control which kind of licensed dependency is loaded and installed. Possible non-free dependencies would be then provided direct on the system. |
| pip | The PyPA recommended tool for installing Python packages | We do not distribute any further package-manager outside our own as there will be never any kind of control which kind of licensed dependency is loaded and installed. Possible non-free dependencies would be then provided direct on the system. |
| conan | A distributed C/C++ package manager | We do not distribute any further package-manager outside our own as there will be never any kind of control which kind of licensed dependency is loaded and installed. Possible non-free dependencies would be then provided direct on the system. |
| cargo | Package manager for Rust | We do not distribute any further package-manager outside our own as there will be never any kind of control which kind of licensed dependency is loaded and installed. Possible non-free dependencies would be then provided direct on the system. |
| chromium | A web browser built for speed and simplicity | See our reasoning here. |
| mumble | A low-latency, high quality voice chat software (client) | Package is demanding protobuf as mandatory dependency. |
| umurmur | Minimalistic Mumble server | Package is demanding protobuf as mandatory dependency. |
| qt-webengine | Provides support for web applications | Package is based fully on chromium. |
Packages and projects using those named dependencies within the listing as mandatory dependency can't and won't be integrated within the repositories of Hyperbola at any time.
The bigger picture and conclusion
While many other systems and system-distributions include those above listed packages in one form or another (other names and descriptions) Hyperbola is oriented fully on the freedom for the users. To keep the packages named is mostly done with the reasoning of convinience, set above freedom and technical emancipation in general.