xmake-repo VS nix-user-chroot

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

> There are workarounds but none of them official.

But does it need to be official? Wouldn't that at the same time bloat nix even more? Isn't it enough if core people of the community for example build https://github.com/nix-community/nix-user-chroot ?

> In reality the only easy way to get it done is to use additional non-foss software

That is not true at all. You can use a nix docker image, a 5 line nix file and 2 commands to do a very basic CI pipeline almost anywhere.

I'm using nix-user-chroot.

Not sure about guix, but for nixos we have https://github.com/nix-community/nix-user-chroot

You could try nix-user-chroot to install Nix and get Sway (and other stuff) that way - no need to compile it yourself.