Move custom software to main git repo
See the blueprint.
A discussion with @segfault convinced me that at least some of the components that currently live in their own Git repo, and that we include as custom Debian packages in the images we build, should instead live in our main tails.git repo. For example, there's very little value in having Tails Greeter in its own repo, while it does significantly increase friction and overhead when working on its codebase.
segfault wrote on #16678:
We maintain some Debian packages which are solely used in Tails and cannot reasonably used outside of Tails. IMO, maintaining these as Debian packages makes our lives unnecessarily harder, because we have to release, build, and upload a new Debian package every time we change something in these packages.
We also share code between the main repo and some packages, which makes it hard to find usages/implementations.
The two packages I currently have in mind are
I propose that we integrate them into the main git repo by copying the files that are installed by the package into
Fully agreed in principle for these 2 repos. Potential difficulties:
tails-persistence-setupmight require special care to keep its own test suite working
- PO/POT files management: currently these are translated under their own Transifex resources; I don't know if/how we can preserve existing translations across this migration
I think WhisperBack and Tails Installer would be good candidates for this first batch too.
Some other candidates (
tails-perl5lib) might be a bit less simple since IIRC RMs need to install the resulting packages on their system, or similar. Let's do some easier ones first :)
Next step: try this for one repo and see how it goes wrt. POT/PO files.