8 comments

[ 3.8 ms ] story [ 26.6 ms ] thread
One could move the "statically build packages, for darwin/linux, with clang" to the "About" section on GitHub.

There are a lot of different environments which a package manager could cover. This is the most important thing for me when learning about new tools: Does it apply to my use case?

This particular one is built around the ideas of bootstrap/reproducibility/hermetcity. If your usecases would benefit from these properties it might apply.

In my opinion the docs need to be improved a lot.

You may want to look at the Bootstrappable Builds project and StageX in order to reduce your binary seeds to almost nothing.

https://bootstrappable.org/ https://lwn.net/Articles/983340/ https://stagex.tools/

Know about it. We have a slightly different model - we use the user's current trusted environment, for example, ubuntu, or fedora, for bootstrap.
None of those environments should be considered trusted; they are not themselves bootstrapped solely from source, they all rely on long chains of their own binaries, and for some things those binaries have relied on external binaries.
There aren't any binary packages or cache yet, but the creator of IX, Anton, has provided a rootfs tarball which uncompresses to about the same size as an installation of Ubuntu on WSL.

Also, I haven't seen anyone other than Anton add new package recipes to the IX repository. The documentation for creating package recipes is at https://stal-ix.github.io/PKG , but it's not referenced by any other page on the stal/IX website.

Patches are most welcome!