manuel
/
live-build
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
live-build/functions/chroot.sh

73 lines
2.1 KiB
Bash
Raw Permalink Normal View History

Adding live-helper 1.0~a1-1.
2007-09-23 08:04:46 +00:00
#!/bin/sh
Updating copyright headers for live-build.
2010-09-02 11:12:37 +00:00
## live-build(7) - System Build Scripts
amend copyright & licensing blocks Current versions of the project files are built upon versions published and licensed by Daniel Baumann, but are modified copies of those files and thus need to be marked as such per licensing requirements (afaik he did not pass along ownership / licensing rights to anyone when he left the project). We should also be careful to not be misrepresenting such modified copies as being attributed to Daniel. Adding a new copyright line referring to "The Debian Live team" should suffice for this. The authorship block in man pages has also similarly been updated. Notes: - tweaked a copy of daniel copyright lines stating 2014 instead of 2015. both of these cases were in files that i had personally introduced in some of my past merged commits that moved some code around. i don't know why they stated 2014. - binary_onie was introduced in 2018, so that has a 2018 date instead of 2016 unlike the rest. - 'efi-image' is a 3rd-party (Canonical Ltd) work that we bundle, but it has been modified by 674794a8f4d61a729d2dbd6d99385d2826138694 and 36a3ba76347ef72df1c316312ed3a26aa4b0c816 so I similarly added a debian live copyright line. - 'grub-cpmodules' is similar. it was only changed by the indentation fix of 36a3ba76347ef72df1c316312ed3a26aa4b0c816 but modification is modification, and this does help cover any possible future changes that might be made.
2020-03-11 09:07:21 -01:00
## Copyright (C) 2016-2020 The Debian Live team
Updating year in copyright notices to 2015.
2015-01-04 18:05:39 -01:00
## Copyright (C) 2006-2015 Daniel Baumann <mail@daniel-baumann.ch>
Updating copyright headers for live-build.
2010-09-02 11:12:37 +00:00
##
Updating GPL standard header in all files.
2012-07-29 23:59:00 +00:00
## This program comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
Updating copyright headers for live-build.
2010-09-02 11:12:37 +00:00
## This is free software, and you are welcome to redistribute it
## under certain conditions; see COPYING for details.
Adding live-helper 1.0~a1-1.
2007-09-23 08:04:46 +00:00
Chroot ()
{
use local scope for private function vars all vars affected have been carefully checked to be quite certain that they are definitely local where variable is assigned the return value of a function/command, the local "declaration" is deliberately done on a separate line, since `local FOO` is actually treated itself as a command rather than a declaration; will thus always cause $? to be zero, and thus if done on the same line as such an assignment can not only clobber $? but in doing so unintentionally blocks failure of a command from triggering the expected exit from having `set -e`. also, from testing, i have found that when assigning "${@}" this must be done on a separate line confusingly as otherwise an error occurs. Gbp-Dch: Short
2020-02-20 05:58:11 -01:00
local CHROOT="${1}"; shift
local COMMANDS
COMMANDS="${@}" #must be on separate line to 'local' declaration to avoid error
Adding live-helper 1.0~a1-1.
2007-09-23 08:04:46 +00:00
# Executing commands in chroot
Adding last modifications in order to have localization fully working in live-helper. This commit goes with some pt_BR translations just for testing. Thanks to Antonio Terceiro for helping and coding in some shell stuff.
2008-08-11 20:28:54 +00:00
Echo_debug "Executing: %s" "${COMMANDS}"
Adding option to allow building in fakeroot/fakechroot environment, thanks to An-Cheng Huang <ancheng@vyatta.com>.
2007-11-10 16:39:49 -01:00
chroot: make var local Gbp-Dch: Short
2020-03-28 13:41:24 -01:00
local ENV=""
For consistency, respecting config/environment too for both chroot and binary environments (but the content of sepcific environments for either chroot or binary still has precedence over the generic one).
2012-06-06 19:32:08 +00:00
use local scope for private function vars all vars affected have been carefully checked to be quite certain that they are definitely local where variable is assigned the return value of a function/command, the local "declaration" is deliberately done on a separate line, since `local FOO` is actually treated itself as a command rather than a declaration; will thus always cause $? to be zero, and thus if done on the same line as such an assignment can not only clobber $? but in doing so unintentionally blocks failure of a command from triggering the expected exit from having `set -e`. also, from testing, i have found that when assigning "${@}" this must be done on a separate line confusingly as otherwise an error occurs. Gbp-Dch: Short
2020-02-20 05:58:11 -01:00
local _FILE
For consistency, respecting config/environment too for both chroot and binary environments (but the content of sepcific environments for either chroot or binary still has precedence over the generic one).
2012-06-06 19:32:08 +00:00
for _FILE in config/environment config/environment.chroot
do
if [ -e "${_FILE}" ]
then
ENV="${ENV} $(grep -v '^#' ${_FILE})"
fi
done
Allowing to inject variables through config/environment.chroot into the chroots environment.
2012-05-24 07:41:27 +00:00
Simpler handling of http proxies There are two main scenarios: 1) The host with live-build is configured to use a proxy This proxy will automatically be used by live-build 2) The user of live-build explicitly specifies a proxy 2A) With the environment variable 'http_proxy' (preferred) 2B) With the command line option --apt-http-proxy Any inconsistency in the setting of a proxy results in an error message of 'lb config' All internal tools (apt/apt-get/aptitude, wget and debootstrap) use the environment variables 'http_proxy' and 'no_proxy', which are passed along to the chroot where needed. Test scenario: - A virtual machine with all out-going traffic blocked, except for the proxy.
2021-04-07 07:10:29 +00:00
${_LINUX32} chroot "${CHROOT}" /usr/bin/env -i HOME="/root" PATH="/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin" TERM="${TERM}" DEBIAN_FRONTEND="${LB_DEBCONF_FRONTEND}" DEBIAN_PRIORITY="${LB_DEBCONF_PRIORITY}" DEBCONF_NONINTERACTIVE_SEEN="true" DEBCONF_NOWARNINGS="true" SOURCE_DATE_EPOCH=${SOURCE_DATE_EPOCH} http_proxy=${http_proxy} no_proxy=${no_proxy} ${ENV} ${COMMANDS}
Adding live-helper 1.0~a10-1.
2007-09-23 08:05:09 +00:00
don't unnecessarily convert exit codes to strings Closes: #952861
2020-02-12 01:40:38 -01:00
return ${?}
Adding live-helper 1.0~a1-1.
2007-09-23 08:04:46 +00:00
}
chroot_live-packages: use dpkg-query to see if a package is installed Closes: #944983
2019-12-19 14:21:58 -01:00
Chroot_has_package() {
use local scope for private function vars all vars affected have been carefully checked to be quite certain that they are definitely local where variable is assigned the return value of a function/command, the local "declaration" is deliberately done on a separate line, since `local FOO` is actually treated itself as a command rather than a declaration; will thus always cause $? to be zero, and thus if done on the same line as such an assignment can not only clobber $? but in doing so unintentionally blocks failure of a command from triggering the expected exit from having `set -e`. also, from testing, i have found that when assigning "${@}" this must be done on a separate line confusingly as otherwise an error occurs. Gbp-Dch: Short
2020-02-20 05:58:11 -01:00
local PACKAGE="${1}"; shift
local CHROOT="${2:-chroot}"; shift
chroot_live-packages: use dpkg-query to see if a package is installed Closes: #944983
2019-12-19 14:21:58 -01:00
if dpkg-query --admindir=${CHROOT}/var/lib/dpkg -s ${PACKAGE} >/dev/null 2>&1 | grep -q "^Status: install"
then
return 0
fi
return 1
}
installer_debian-installer: don't mess with /var/lib/dpkg/status Use a similar trick as for chroot_live-packages. Relates to #944983.
2019-12-19 14:53:30 -01:00
Chroot_package_list() {
use local scope for private function vars all vars affected have been carefully checked to be quite certain that they are definitely local where variable is assigned the return value of a function/command, the local "declaration" is deliberately done on a separate line, since `local FOO` is actually treated itself as a command rather than a declaration; will thus always cause $? to be zero, and thus if done on the same line as such an assignment can not only clobber $? but in doing so unintentionally blocks failure of a command from triggering the expected exit from having `set -e`. also, from testing, i have found that when assigning "${@}" this must be done on a separate line confusingly as otherwise an error occurs. Gbp-Dch: Short
2020-02-20 05:58:11 -01:00
local CHROOT="${1:-chroot}"; shift
installer_debian-installer: don't mess with /var/lib/dpkg/status Use a similar trick as for chroot_live-packages. Relates to #944983.
2019-12-19 14:53:30 -01:00
dpkg-query --admindir=${CHROOT}/var/lib/dpkg -W -f'${Package}\n'
}
Added the option to include files before and after package installation Moved includes.chroot to includes.chroot_after_packages and added includes.chroot_before_packages. includes.chroot does still work as before. We also now use rsync for copying files if it is installed. This improves runtime and space consumption for large includes. Gbp-Dch: Short Closes: #927128
2020-10-27 14:07:11 -01:00
Chroot_copy_dir() {
local DIR="${1}"
local NAME="${2:-$(basename ${DIR})}"
Check_installed host /usr/bin/rsync rsync
if [ "${INSTALL_STATUS}" -eq "0" ]
then
Echo_message "Copying ${NAME} into chroot using rsync..."
rsync -Klrv --chown=0:0 "${DIR}" chroot/
else
cd "${DIR}"
Echo_message "Creating a tarball with files from ${NAME}..."
tar cf "${OLDPWD}"/chroot/"${NAME}".tar .
cd "${OLDPWD}"
Echo_message "Extracting the tarball in the chroot..."
Chroot chroot "tar -xvf ${NAME}.tar --no-same-owner --keep-directory-symlink --overwrite"
rm chroot/"${NAME}".tar
fi
}