manuel
/
live-build
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
live-build/scripts/build/bootstrap_cache

84 lines
1.7 KiB
Plaintext
Raw Normal View History

Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
#!/bin/sh
## 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>
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
##
## This program comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
## under certain conditions; see COPYING for details.
set -e
# Including common functions
[ -e "${LIVE_BUILD}/scripts/build.sh" ] && . "${LIVE_BUILD}/scripts/build.sh" || . /usr/lib/live/build.sh
# Setting static variables
help/usage: fix overly complex script description handling Closes: #952887
2015-02-05 02:30:47 -01:00
DESCRIPTION="Cache bootstrap stage"
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
USAGE="${PROGRAM} [--force]"
tidy script init (1/4) - arg and config processing Partial fix for #952919 Gbp-Dch: Short
2015-02-05 02:30:47 -01:00
# Processing arguments and configuration files
Init_config_data "${@}"
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
# Check architecture
Check_crossarchitectures
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
if ! In_list "bootstrap" ${LB_CACHE_STAGES}
then
exit 0
fi
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
stagefiles: further robustify with auto filenames as suggested by Raphaël rather than have fixed stagefile filename strings at all in the scripts, use `$(basename $0)` to use the name of the script (which is the same for almost all cases anyway, and the stage files are supposed to be almost exclusively unique per-script). we can thus simplify things by determining the filename for most use cases within the functions themselves. this does change the file used by a couple of scripts, affecting backwards compatibility of executing live-build upon an existing partially or fully completed build: - binary_grub-pc used "binary_grub" - chroot_includes used "includes.chroot" care had to be taken for the following cases: - there are some cases like bootstrap_cache, source_debian and bootstrap_debootstrap which are dealing with more than one file, and/or otherwise a filename that is not specific to the script itself exactly, or should not be based upon its name. - some cases like chroot_cache, bootstrap_cache and chroot_install-packages need to append something to the end of the name depending upon which pass/action mode the script is being executed with. - furthermore in the bootstrap_cache case one of the filenames is used within the bootstrap_debootstrap and thus needs very careful handling to be certain that a change in filename of bootstrap_cache does not break bootstrap_debootstrap. Gbp-Dch: Short
2020-03-13 16:11:53 -01:00
_ACTION="${1}"
shift
# Set non-default stage file name (auto picked up by the functions)
stagefiles: simplify & robustify - avoid all need to pass ".build/" path in stage file names into the functions - add a helper to remove a stage file (required to complete the above properly) - avoid duplicating filenames within scripts which makes them prone to mistakes (some instances of which I've actually encountered and had to fix) Gbp-Dch: Short
2020-03-12 00:21:39 -01:00
# Note, this (plus the applicable extension added below) must match that used in `bootstrap_debootstrap`
stagefiles: further robustify with auto filenames as suggested by Raphaël rather than have fixed stagefile filename strings at all in the scripts, use `$(basename $0)` to use the name of the script (which is the same for almost all cases anyway, and the stage files are supposed to be almost exclusively unique per-script). we can thus simplify things by determining the filename for most use cases within the functions themselves. this does change the file used by a couple of scripts, affecting backwards compatibility of executing live-build upon an existing partially or fully completed build: - binary_grub-pc used "binary_grub" - chroot_includes used "includes.chroot" care had to be taken for the following cases: - there are some cases like bootstrap_cache, source_debian and bootstrap_debootstrap which are dealing with more than one file, and/or otherwise a filename that is not specific to the script itself exactly, or should not be based upon its name. - some cases like chroot_cache, bootstrap_cache and chroot_install-packages need to append something to the end of the name depending upon which pass/action mode the script is being executed with. - furthermore in the bootstrap_cache case one of the filenames is used within the bootstrap_debootstrap and thus needs very careful handling to be certain that a change in filename of bootstrap_cache does not break bootstrap_debootstrap. Gbp-Dch: Short
2020-03-13 16:11:53 -01:00
STAGE_FILE="bootstrap_cache.${_ACTION}"
stagefiles: simplify & robustify - avoid all need to pass ".build/" path in stage file names into the functions - add a helper to remove a stage file (required to complete the above properly) - avoid duplicating filenames within scripts which makes them prone to mistakes (some instances of which I've actually encountered and had to fix) Gbp-Dch: Short
2020-03-12 00:21:39 -01:00
stagefiles: further robustify with auto filenames as suggested by Raphaël rather than have fixed stagefile filename strings at all in the scripts, use `$(basename $0)` to use the name of the script (which is the same for almost all cases anyway, and the stage files are supposed to be almost exclusively unique per-script). we can thus simplify things by determining the filename for most use cases within the functions themselves. this does change the file used by a couple of scripts, affecting backwards compatibility of executing live-build upon an existing partially or fully completed build: - binary_grub-pc used "binary_grub" - chroot_includes used "includes.chroot" care had to be taken for the following cases: - there are some cases like bootstrap_cache, source_debian and bootstrap_debootstrap which are dealing with more than one file, and/or otherwise a filename that is not specific to the script itself exactly, or should not be based upon its name. - some cases like chroot_cache, bootstrap_cache and chroot_install-packages need to append something to the end of the name depending upon which pass/action mode the script is being executed with. - furthermore in the bootstrap_cache case one of the filenames is used within the bootstrap_debootstrap and thus needs very careful handling to be certain that a change in filename of bootstrap_cache does not break bootstrap_debootstrap. Gbp-Dch: Short
2020-03-13 16:11:53 -01:00
case "${_ACTION}" in
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
restore)
# Checking stage file
stagefiles: simplify & robustify - avoid all need to pass ".build/" path in stage file names into the functions - add a helper to remove a stage file (required to complete the above properly) - avoid duplicating filenames within scripts which makes them prone to mistakes (some instances of which I've actually encountered and had to fix) Gbp-Dch: Short
2020-03-12 00:21:39 -01:00
Check_stagefile "${STAGE_FILE}"
bootstrap: only output message where actually applicable Gbp-Dch: Ignore Closes: #952848
2015-01-07 04:02:13 -01:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
if [ -d cache/bootstrap ]
then
Echo_message "Restoring bootstrap stage from cache..."
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
fix comment typo Gbp-Dch: Ignore
2020-03-13 15:19:59 -01:00
# Acquire lock file
locks: tidy lock acquisition Combine the check+create done in each script. (The original functions are still callable as before, but a new combined `Aquire_lockfile` function can be called instead, as now used). Note, a further simplification could be done in removing the passing of the lock filename in as a parameter since every use of the functions is with ".lock". The lock functions already have a fallback to ".build/lock" though. Checking the history, the fallback used to be for a system wide lock, which was then replaced with this config-tree specific one. As long as that is not used implicitly by 3rd-party hooks then surely we are free to change the fallback to ".lock" and further remove passing in a name as a param...? history: db5d2b0dcdae96e712661605e17bc9875e224f9f 0aa8289a3773fd8a3885090b72622c2f95ab099c Gbp-Dch: Short Closes: #952918
2015-02-05 02:30:47 -01:00
Acquire_lockfile
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
# Removing old chroot
rm -rf chroot
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
# Restoring old cache
cp -a cache/bootstrap chroot
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
# Creating stage file
stagefiles: simplify & robustify - avoid all need to pass ".build/" path in stage file names into the functions - add a helper to remove a stage file (required to complete the above properly) - avoid duplicating filenames within scripts which makes them prone to mistakes (some instances of which I've actually encountered and had to fix) Gbp-Dch: Short
2020-03-12 00:21:39 -01:00
Create_stagefile "${STAGE_FILE}"
stagefiles: further robustify with auto filenames as suggested by Raphaël rather than have fixed stagefile filename strings at all in the scripts, use `$(basename $0)` to use the name of the script (which is the same for almost all cases anyway, and the stage files are supposed to be almost exclusively unique per-script). we can thus simplify things by determining the filename for most use cases within the functions themselves. this does change the file used by a couple of scripts, affecting backwards compatibility of executing live-build upon an existing partially or fully completed build: - binary_grub-pc used "binary_grub" - chroot_includes used "includes.chroot" care had to be taken for the following cases: - there are some cases like bootstrap_cache, source_debian and bootstrap_debootstrap which are dealing with more than one file, and/or otherwise a filename that is not specific to the script itself exactly, or should not be based upon its name. - some cases like chroot_cache, bootstrap_cache and chroot_install-packages need to append something to the end of the name depending upon which pass/action mode the script is being executed with. - furthermore in the bootstrap_cache case one of the filenames is used within the bootstrap_debootstrap and thus needs very careful handling to be certain that a change in filename of bootstrap_cache does not break bootstrap_debootstrap. Gbp-Dch: Short
2020-03-13 16:11:53 -01:00
Create_stagefile "bootstrap"
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
exit 0
fi
;;
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
save)
Echo_message "Saving bootstrap stage to cache..."
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
# Checking stage file
stagefiles: simplify & robustify - avoid all need to pass ".build/" path in stage file names into the functions - add a helper to remove a stage file (required to complete the above properly) - avoid duplicating filenames within scripts which makes them prone to mistakes (some instances of which I've actually encountered and had to fix) Gbp-Dch: Short
2020-03-12 00:21:39 -01:00
Check_stagefile "${STAGE_FILE}"
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
fix comment typo Gbp-Dch: Ignore
2020-03-13 15:19:59 -01:00
# Acquire lock file
locks: tidy lock acquisition Combine the check+create done in each script. (The original functions are still callable as before, but a new combined `Aquire_lockfile` function can be called instead, as now used). Note, a further simplification could be done in removing the passing of the lock filename in as a parameter since every use of the functions is with ".lock". The lock functions already have a fallback to ".build/lock" though. Checking the history, the fallback used to be for a system wide lock, which was then replaced with this config-tree specific one. As long as that is not used implicitly by 3rd-party hooks then surely we are free to change the fallback to ".lock" and further remove passing in a name as a param...? history: db5d2b0dcdae96e712661605e17bc9875e224f9f 0aa8289a3773fd8a3885090b72622c2f95ab099c Gbp-Dch: Short Closes: #952918
2015-02-05 02:30:47 -01:00
Acquire_lockfile
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
rm -rf cache/bootstrap
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
mkdir -p cache
Moving partial python rewrite to separate branch, let's do it in the jessie+1 cycle rather than go with the current mixed code.
2014-08-27 21:14:12 +00:00
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
cp -a chroot cache/bootstrap
# Creating stage file
stagefiles: simplify & robustify - avoid all need to pass ".build/" path in stage file names into the functions - add a helper to remove a stage file (required to complete the above properly) - avoid duplicating filenames within scripts which makes them prone to mistakes (some instances of which I've actually encountered and had to fix) Gbp-Dch: Short
2020-03-12 00:21:39 -01:00
Create_stagefile "${STAGE_FILE}"
simplify STAGE checks - use In_List Closes: #952917
2015-01-06 02:43:43 -01:00
;;
esac