Where are the problems of Hyperbola? Could you specify these a bit more? Yes, Guix has very interesting features. But also within the repositories there are problematic packages like Rust, Mono and OpenJDK. Those were identified as problematic regarding licensing for example. So how to "solve problems" being not declared further here and creating even new ones regarding freedom for example?

Not meant as attacking any position, but in regards it should be the personal decision of every individual what to install and I think Hyperbola does a very good job about this. Yes, some packages are older, but this can also be solved: Either building own packages or using software like GUIX, like here.

Well, as you've said: There is the discussion about usability vs. security. Packages are in many ways not the newest one but having two different package-management systems is also quite not the best idea. So distributing GUIX is a decision from the user-perspective and it is a good one when fitting the needs. But it can also be quite not the best one for everyone else. As I'm also a user here: Yes, I've looked into this and want to try GUIX out as testing scenario. But there are also quite some problems, not only the ones I've mentioned about licensing and the on-going pragmatism against any kind of ideal in regards of "free, libre soft- and hardware".

So my question was just taken from the user-perspective. Otherwise around we should wait what the development and the team behind are saying onwards this proposal itself. There is also the question for creating OpenRC-services and much more. Modifying GUIX to disallow some packages is even more complicated as blacklisting always is and you have to be always onto the listing of newer added packages for Rust, Java / OpenJDK and Mono. So even more work to do!

Besides there is always the possibility to propose own and newer packages on LibreGit or here in the forums. So if you want we can start here and create an own package for installation of GUIX, a PKGBUILD either to compile that from source or distribute a binary version. Hyperbola is free software and we can "hack" this software, modify it for our needs and offer our changes for others. This is what I've learned and the PKGBUILD-format as pacman or in the future hyperman is such a good possibility to build and share own modifications.

A good question: Don't know so far as only the developers can say more about the future. But as far as we know hyperman could be used in the future for HyperbolaBSD as it is built onto that base. Perhaps we can use it the same as pacman today but I'm not really sure about if HyperbolaBSD will use some kind of system similar to "ports" of OpenBSD. Would be definitely interesting building packages the same way as for now!

Regarding the package for GUIX: This is and was of course an invitation for everybody interested. I'm definitely one person willing to look into this as I find the base absolutely interesting - have used GuixSD some time ago.

Done!

Don't know how this works here in the forum as I've used just the link "Email" and the system showed me that the message was sent. Well: Other way also possible to write down the notes here as it could be also of interest for others.

Will try otherwise but only within a few days (can't name more closely as there is much to do within the next time).
For now I'll leave some short notes and links for the first startup:

PKGBUILD on the AUR

https://aur.archlinux.org/cgit/aur.git/ … ILD?h=guix

Whole package-files on the AUR

https://aur.archlinux.org/cgit/aur.git/tree/?h=guix

initd-script from Gentoo-overlays

https://data.gpo.zugaina.org/nix-guix/s … emon.initd

Thanks!
In short: Yes. But there is more: Looking at the dependencies needs also some more buildout.

makedepends=(
  'bash-completion'
  'fish'
  'guile-json'
  'guile-ssh>=0.10.2'
  'help2man')
depends=(
  'guile>=2.0.9'
  'guile-git-lib'
  'guile-sqlite3'
  'sqlite>=3.6.19'
  'bzip2'
  'gnutls'
  'libgcrypt'
  'zlib')

So all packages should be installed and available. Therefore also corresponding PKGBUILD-files for creation. After the basic dependencies are available, there is GUIX in general. So I would first try to build it with "systemd" activated. Afterwards we can use the initd-configuration coming from Gentoo to recreate the package for Hyperbola.

The usage of "systemd" was only meant for the first test to compile the package, not for the final steps. When you have the package right away functional on this level we can provide the initd-script more easily. But, yes: It can also be done directly or without any further execution for any init-system right away, just for testing purpose of compilation and running the build therefore manually.

To use PKGBUILD all steps have to fit in the end, but as mentioned: This packaging-system is handled very good and you can debug problems without further problems. Of course, precise steps needed when being finalized as this should be a running daemon on the system. I think GUIX is also mentioning nscd to be running? So this should be also noted (Link).

I use lxdm, so I don't have an answer at the moment regarding why sddm makes errors.

From what I have read Guix has no further dependencies from the installed operating-system and can run instead just with some basic packages. Meaning: Installing applications like Jami would be no further problem. Nevertheless the repositories of Guix have enough questionable packages as mentioned that have questionable licensing being not fully compliant with the principles of Hyperbola, some even are itself a security risk like Ungoogled Chromium as this project can never be free itself.

So besides getting this to run Guix has own package-repositories with questionable content. That's the reasoning to discuss from my point of view besides having another managing platform for packages besides pacman. But everyone is free to hack and modify the system for own needs and to share the knowledge for the modifications. The core team is reading here the forums as we do, so we can wait for an answer or you check out for the IRC as proposal.

Ok, then hyperbola needs guix.

In case of strange packages, the solution is so simple. You make something like hyperguix. You take instructions and if they point to a nonfree package, you throw an error. And if the package is available, you go ahead and pass that request to guix server. It's trivial guys. It's a piece of cake. You give a command like

 hguix install __ 

I get it. So with something like hyperguix, hyperbola will have to keep updating the blacklist as per the uploads of packages on guix page. If guix would facilitate nonfree software, then even having a pkgbuild for guix will assist users on hyperbola to install it. One would want to make it difficult for users to install nonfree software as it is now. BTW, what is white hole? I'm unable to enter it from outside! ;D