Install Tails' fork of live-build from a submodule.
Previously, live-build was installed from custom-built Debian packages. This patch instead adds the custom fork as a git submodule, cutting out the packaging from development and testing.
@intrigeri notes:
After second thought, maybe it's a good time to stop using a (custom fork of an ancient) Debian package for live-build: this makes it difficult to prepare and correctly test such contributions (you basically have to build & upload a package to test any change), and painful to review/test/accept them. I already noticed that when I was working on squashfs-tools-ng and zstd compression myself recently. I'm under the impression that historically, this has negatively impacted our motivation to work on anything that required patching live-build.
So, we could:
Add our live-build repo as a Git submodule of tails/tails, in some relevant place under vagrant/
In the Vagrant box build process, somehow copy the relevant live-build files to the VM filesystem; this may boil down to running DESTDIR=something make install
These steps are done.
- In the code that determines which Vagrant box shall be used (and if necessary, first built): take into account the status of the live-build submodule, if not done for free thanks to step 1
I investigated this, but couldn't find that code.
Open question: Is the version in /etc/amnesia/version supposed to be machine readable, i.e. did I break something by using git submodule status there?