summaryrefslogtreecommitdiffstats
path: root/data
Commit message (Collapse)AuthorAgeFilesLines
* Adjust dpkg-divert path: it has moved.intrigeri2016-12-201-1/+1
|
* apt-get wrapper: purge and remove actions can trigger the installation (and ↵intrigeri2016-05-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | thus, the download) of packages. As noticed by anonym (https://labs.riseup.net/code/issues/10748#note-32), lockfile-progs is missing from the build manifest. Indeed, it is installed by a call to `apt-get purge', found in config/chroot_local-hooks/98-remove_unwanted_packages, whose effect is: The following extra packages will be installed: lockfile-progs The following packages will be REMOVED: apt-listchanges* at* autoconf* automake* bsd-mailx* dc* debian-faq* doc-debian* exim4* exim4-base* exim4-config* exim4-daemon-light* ftp* m4* mlocate* mutt* ncurses-term* nfs-common* procmail* python-reportbug* reportbug* telnet* texinfo* time* w3m* wamerican* The following NEW packages will be installed: lockfile-progs For the curious: monkeysphere "Depends: lockfile-progs | procmail", so when we remove procmail, apt-get installs lockfile-progs to satisfy the dependency.
* apt-get wrapper: add support for the "check" mode, that libdvd-pkg uses.intrigeri2016-05-121-1/+1
|
* Patch the "jessie" debootstrap script at build time, instead of shipping a ↵intrigeri2016-05-112-208/+11
| | | | forked version of it.
* apt-get wrapper: deal with an unlikely corner case.intrigeri2016-05-111-1/+3
| | | | | | | | | | | We know that apt-get's action (install, update, etc.) will come _before_ any package name, so as soon as we see a supported action, we stop looking for one. The only problem left is if apt-get is called with an unsupported action, followed by a package name equal to one of our supported actions. If this were to happen, even though unlikely, then mode=$package and likely the resulting apt-get command-line should be invalid or break the build sooner or later, so I'm not too concerned about this breaking stuff without us noticing immediately.
* Move gen-manifests.pl to a better place, and give it a less ambiguous name.intrigeri2016-03-101-89/+0
| | | | | | | This is where other auxiliary build scripts run before or after live-build are stored. Refs: #10748
* Add basic manifest generator.Cyril Brulebois2016-03-101-0/+89
| | | | | | | | | | The generated manifest consists of: - A list of origins and relevant references. XXX: feed references once build system updates are implemented. - A list of binary and source packages, per-origin, with both package name and version. Signed-off-by: Cyril Brulebois <cyril@debamax.com>
* Add apt-get wrapper.Cyril Brulebois2016-03-102-0/+50
| | | | | | | | | | | | | | | This wrapper makes it possible to keep track of both binary and source package downloads, by writing /debootstrap/{bin,src}uris respectively, alongside the debootstrap-generated /debootstrap/deburis (for binary downloads during bootstrap phase). Each file follows the following format: package version uri The source uri only contains the dsc file, but it would be easy to list all files if later needed. Signed-off-by: Cyril Brulebois <cyril@debamax.com>
* XXX: Use a custom debootstrap script.Cyril Brulebois2016-03-101-0/+204
| | | | | | | | | | | | | | | | | | Setting this variable makes it possible to keep on using wheezy across the whole live build process, except for the debootstrap step. This modified copy of the wheezy script tweaks the environment before live-build moves from the bootstrap step to the chroot step (package installation etc.). NOTE: Another way to implement this would be to insert some live-build hooks between bootstrap and build steps, but it appears such hooks aren't supported. XXX: Having a whole copy made development easier, but on the long run it would be better to apply a patch to the wheezy script to ensure further maintenance. Signed-off-by: Cyril Brulebois <cyril@debamax.com>
* Add more contrast to splash screenTails developers2014-04-251-0/+0
| | | | | | For some reason, the splash screen appears much darker in syslinux than the original image is, either in full colors, either in 65536 colors. Adding more contrast solves this.
* Reconvert the splash screenTails developers2014-04-161-0/+0
| | | | | | This time uses: convert -depth 16 -colors 65536 splash-full-colors.png splash.png
* Replace boot splashTails developers2014-04-161-0/+0
|
* syslinux: custom splashTails developers2012-05-111-0/+0
|
* Add custom splash screen.T(A)ILS developers2011-02-171-0/+0
This image is the standard live-build one, with the "Live" part of the text moved to the right so that our languages menu is not displayed on top of it... and therefore unreadable.