xmake-repo VS nix-installers

xmake [1] gives you something like this via `xrepo env shell`.

[1] https://xrepo.xmake.io/

This project should also soon be available on xrepo, right now you can copy the headers or use the package in `package.lua` to install.

Yes, although the documentation seems bare-bones, the code looks clean.

The xmake package repository files might be useful also for people interested in making their own package manager, or even installing by hand.

Here is the package information for autoconf, for instance:

https://github.com/xmake-io/xmake-repo/blob/master/packages/...

It has download links, checksums for specific versions, and the Lua syntax seems easy to parse.

The package for NanoVG however, does not indicate anywhere that you need the GLEW and GLFW libraries:

https://github.com/xmake-io/xmake-repo/blob/master/packages/...

Therefore, if the official xmake-repo repository already provides the required package, you can use it directly without specifying the package namespace.

I written a c/c++ package manager https://xrepo.xmake.io/#/

Currently, we have included the following toolchain packages in the xmake-repo repository, allowing xmake to pull and integrate remotely:

Here's the github page for xrepo: https://github.com/xmake-io/xmake-repo

If you install it from the community RPM installer, it works as they have SELinux support added: https://github.com/nix-community/nix-installers

I tried to install the Nix package manager on my Fedora 37 machine. Having read about some issues with installing Nix with the install script on Fedora and other OS, using Selinux, I chose install via "nix-installers" rpm-packe (https://github.com/nix-community/nix-installers/issues/16). Unfortunately, I get warnings about created uids throughout the install process not being in the scope of `SYS_UID_MAX 999`. Furthermore, after rebooting the computer, I end up with a flickering black screen instead of on my (Gnome) Desktop environment.

Looks like you already found u/adisbladis legacy installers and opened a feature request for Silverblue support. Your best bet would be to start learning how SELinux policies work and see if you can adapt those for the way that you've set up Silverblue, or to see if you can modify the RPM builder to accommodate Silverblue by putting the Nix store under /var and bind mounting it onto /nix, like those other instructions floating around do.

There's work to add nix to silverblue via community packaging: https://github.com/nix-community/nix-installers/pull/8

I think nonguix also uses equivalent machinery for its Steam package: https://gitlab.com/nonguix/nonguix/-/blob/master/nongnu/pack...

Maybe there are docs on repurposing that someone more familiar with nonguix can point to.

Apparently there is an rpm-ostree-friendly RPM build of Nix that can be used to install Nix on Silverblue as well: https://github.com/nix-community/nix-installers/pull/8

It includes some code to get around the group/user management quirks that some other commenters have noted b0rked the Guix installer, so perhaps it gives an outline of how to install Guix on Silverblue for a hacker who'd like to try it :)