write blog posts

[stapelberg]

independent:

• [x] no hooks/triggers and how to construct a working system without them
  • upstream software hygiene: update path, good cache design
  • move work from install-time to run-time

introducing distri:

• [x] read-only SquashFS images, package store, package part of path hierarchy, FHS compatibility file system layout
• [x] package manager/build tool based on the above
  • extremely fast thanks to append-only store (no fsync), missing unpack step, no hooks/triggers (→ concurrency)
  • this extends to building packages, creating images and installing a system to disk
• [ ] hermetic packages
  • single lib dir with symlinks instead of large rpath
  • wrapper program details
  • no need to ship duplicate copies of libraries as long as you have an immutable package store
  • together with separate hierarchies this allows for co-installability (no conflicts)
  • conflicts moved to FHS compat/exchange dirs, but that’s for users only

later:

• [ ] declarative packaging (build.textproto, extracting info from pkg-config files, etc.)
• [ ] remote builds

[stapelberg]

https://michael.stapelberg.ch/posts/2019-08-17-introducing-distri/ is now published, removing the release blocker label.