knit
apt2ostree
knit | apt2ostree | |
---|---|---|
4 | 6 | |
181 | 93 | |
- | - | |
6.4 | 0.0 | |
8 months ago | over 1 year ago | |
Go | Python | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
knit
-
Why Use Make
I've been working on a tool called Knit (https://github.com/zyedidia/knit) that I think is similar to what you are looking for. Essentially, a Knitfile is a Lua program with Make's declarative rule syntax baked in. It is like Make (with some additional changes inspired by Plan9 mk), but where Make's custom scripting language is replaced with Lua. It's still in progress (I'm currently using it in some projects, and then will likely make some more changes based on my experiences), but I hope to release a stable version in the next few months. If you or others also have feedback, please let me know!
- Knit: a simple and powerful build tool using Lua, inspired by make/mk
- Knit: a simple and powerful build tool using Lua, inspired by make/mk.
apt2ostree
-
Why Use Make
Hm yes now I remember that point about how the data is anonymous Python objects that you can pass around to functions.
Are there any open source examples? I looked around the github account, but I mostly remember this tool
https://github.com/stb-tester/apt2ostree
I'd be interested in seeing the Python config and Ninja output, to see how it works. Right now it looks to me like the dependencies are more implicit than explicit, e.g. with your copen example
---
The system I ended up with is more like Bazel, but it's not building containers, so it's a slightly different problem. But I'm interested in building containers incrementally without 'docker build'.
I like the apt lockfile idea definitely ... However I also have a bunch of other blobs and tarballs, that I might not want to check into git. I guess you just put those in OSTree?
Our config looks like this
https://github.com/oilshell/oil/blob/master/core/NINJA_subgr...
And all the code is in build/ninja* of the same repo
-
An ode to Flatpak (and Fedora Silverblue)
However, you can get pretty close yourself with a tool like this https://github.com/stb-tester/apt2ostree
-
Docker containers usually still reachable even if bound to 127.0.0.1
With apt2ostree[1] we use lockfiles to allow us to version control the exact versions that were used to build a container. This makes updating the versions explicit and controlled, and building the containers functionally reproducible - albeit not byte-for-byte reproducible.
[1]: https://github.com/stb-tester/apt2ostree#lockfiles
-
Any plans for an immutable Debian desktop?
If you have time to test things, you can try to use ostree to manage a Debian installation. This is what Silverblue uses. Their is already a tool to create APT-based ostree images.
- Lockfiles for packages in a Debian/Ubuntu rootfs
-
Reproducible builds for Debian: a big step forward
On the subject of reproducible debian-based environments I wrote apt2ostree[1]. It applies the cargo/npm lockfile idea to debian rootfs images. From a list of packages we perform dependency resolution and generate a "lockfile" that contains the complete list of all packages, their versions and their SHAs. You can commit this lockfile to git.
You can then install Debian or Ubuntu into a chroot just based on this lockfile and end up with a functionally reproducible result. It won't be completely byte identical as your SSH keys, machine-id, etc. will be different between installations, but you'll always end up with the same packages and package versions installed for a given lockfile.
This has saved us on a few occasions where an apt upgrade had broken the workflow of some of our customers. We could see exactly which package versions changed in git history and roll-back the problematic package before working on fixing it properly. This is vastly better than the traditional `RUN apt-get install -y blah blah` you see in `Dockerfile`s.
IMO it's also more convenient than debootstrap as you don't need to worry about gpg keys, etc. when building the image. Dependency resolution and gpg key stuff is done at lockfile generation time, so the installation process can be much simpler. In theory it could be made such that only dpkg is required to do the install, rather than the whole of apt, but that's by-the-by.
apt2ostree itself is probably not interesting to most people as it depends on ostree and ninja but I think the lockfile concept as applied to debian repos could be of much broader interest.
[1]: https://github.com/stb-tester/apt2ostree#lockfiles
[2]: https://ostreedev.github.io/ostree/
What are some alternatives?
monadic-arrays - MArray instances for monad transformers
ostree - Operating system and container binary deployment and upgrades
distributive - Dual Traversable
chromium - The official GitHub mirror of the Chromium source
subwordgraph - An implementation of a classic Subword Graph (also known as Directed Acyclic Word Graph).
rkt
world-atlas - Pre-built TopoJSON from Natural Earth.
eget - Easily install prebuilt binaries from GitHub.
us-atlas - Pre-built TopoJSON from the U.S. Census Bureau.
singularity - SingularityCE is the Community Edition of Singularity, an open source container platform designed to be simple, fast, and secure.
nibblestring - Packed, strict nibble arrays with a list interface (ByteString for nibbles)
office365-pol - [OUTDATED] A PlayOnLinux script that utilizes the version of Wine made for CrossOver to run Microsoft 365 Apps / Office 365 without requiring any paid CrossOver components