Project

General

Profile

Feature #7036

Move custom software to main git repo

Added by intrigeri over 5 years ago. Updated 23 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Starter:
No
Affected tool:

Description

See the blueprint.


Subtasks

Feature #16912: Move greeter source to main git repoNeeds Validationanonym

Feature #16935: Move tailslib to main repoIn Progresssegfault

Feature #16936: Move whisperback source to main repoConfirmedsegfault


Related issues

Related to Tails - Feature #5506: Split Git Rejected 09/11/2013
Related to Tails - Feature #7087: Do not bundle Tor Launcher in the main Tails Git repository Resolved 04/15/2014
Related to Tails - Feature #6220: Automated Debian package build infrastructure Confirmed 08/07/2013
Related to Tails - Feature #9171: Refactor tails-custom-apt-sources and tails-diff-suite duplicated code Confirmed 04/07/2015
Related to Tails - Feature #7221: Write a script that deletes old merged Git branches Resolved
Related to Tails - Feature #15864: Make onboarding of new developers easier In Progress 08/30/2018
Related to Tails - Bug #15778: Make the Tails Installer upstream tarball DFSG-free Confirmed 08/09/2018
Related to Tails - Feature #16095: Curate the list of languages in Tails Greeter Confirmed 11/04/2018
Duplicated by Tails - Feature #16678: Integrate Tails-specific Debian packages into the main git repo Duplicate

History

#1 Updated by intrigeri over 5 years ago

#2 Updated by intrigeri about 5 years ago

  • Related to Feature #7087: Do not bundle Tor Launcher in the main Tails Git repository added

#3 Updated by intrigeri about 5 years ago

  • Subject changed from Manage custom software as Git submodules to Manage custom software as Git submodules or similar
  • Type of work changed from Code to Research

#4 Updated by intrigeri about 5 years ago

  • Blueprint set to https://tails.boum.org/blueprint/Git_sub-repositories/

#5 Updated by intrigeri about 5 years ago

  • Description updated (diff)

#6 Updated by intrigeri about 5 years ago

  • Related to Feature #6220: Automated Debian package build infrastructure added

#7 Updated by intrigeri over 4 years ago

  • Related to Feature #9171: Refactor tails-custom-apt-sources and tails-diff-suite duplicated code added

#8 Updated by intrigeri over 4 years ago

  • Related to Feature #7221: Write a script that deletes old merged Git branches added

#9 Updated by intrigeri 4 months ago

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.

#10 Updated by intrigeri 4 months ago

  • Related to Feature #15864: Make onboarding of new developers easier added

#11 Updated by intrigeri 4 months ago

  • Duplicated by Feature #16678: Integrate Tails-specific Debian packages into the main git repo added

#12 Updated by intrigeri 4 months ago

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 tails-greeter and tails-persistence-setup.

I propose that we integrate them into the main git repo by copying the files that are installed by the package into config/chroot_local_includes.

Fully agreed in principle for these 2 repos. Potential difficulties:

  • tails-persistence-setup might 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-iuk, 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.

#13 Updated by segfault 29 days ago

  • Assignee set to segfault

#14 Updated by segfault 29 days ago

  • Subject changed from Manage custom software as Git submodules or similar to Move custom software to main git repo

#15 Updated by segfault 29 days ago

I would like to start with the greeter, and then move pythonlib to config/chroot_local_includes.

#16 Updated by intrigeri 16 days ago

  • Related to Bug #15778: Make the Tails Installer upstream tarball DFSG-free added

#17 Updated by sajolida 8 days ago

  • Related to Feature #16095: Curate the list of languages in Tails Greeter added

Also available in: Atom PDF