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

1 files changed, 4 insertions, 10 deletions

diff --git a/scripts/build/bootstrap_cache b/scripts/build/bootstrap_cache
index 5ed474090..994cf82cf 100755
--- a/scripts/build/bootstrap_cache
+++ b/scripts/build/bootstrap_cache
@@ -38,11 +38,8 @@ case "${1}" in
 		then
 			Echo_message "Restoring bootstrap stage from cache..."
 
-			# Checking lock file
-			Check_lockfile .lock
-
-			# Creating lock file
-			Create_lockfile .lock
+			# Aquire lock file
+			Acquire_lockfile
 
 			# Removing old chroot
 			rm -rf chroot
@@ -64,11 +61,8 @@ case "${1}" in
 		# Checking stage file
 		Check_stagefile .build/bootstrap_cache.save
 
-		# Checking lock file
-		Check_lockfile .lock
-
-		# Creating lock file
-		Create_lockfile .lock
+		# Aquire lock file
+		Acquire_lockfile
 
 		rm -rf cache/bootstrap