9079079092
The docker-run script attempts to support git-new-workdirs and git-worktrees by resolving the symlink at '$GIT_DIR/config' to get the true $GIT_DIR. However this does not work for git-worktrees as they do not use symlinks, instead they change the $GIT_DIR into a regular file that contains the path to the real $GIT_DIR. To complicate things further, we actually want the $GIT_COMMON_DIR which is the superset of a worktree's $GIT_DIR. git-rev-parse supports the '--git-common-dir' which will resolve the $GIT_COMMON_DIR for us. However it does not work for git-new-workdirs, so we still need to detect and handle them. '--git-common-dir' also appeared only with git 2.10.0, released in 2016, so it will not be available in older "enterprise-grade" distributions. In that case, 'git rev-parse --git-common-dir' would return the option flag '--git-common-dir' as-is, which is incorrect. So, we instruct it to never return flags. '--git-common-dir' also returns just '.git' for the main working copy, but 'docker run' want an absolute path, so we canonicalise it. Signed-off-by: Brandon Maier <brandon.maier@collins.com> [yann.morin.1998@free.fr: - support git versions before --git-common-dir was introduced - don't mount GIT_DIR if unknown (i.e. not needed) - fix expanding MAIN_DIR ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
---|---|---|
.. | ||
checkpackagelib | ||
checksymbolslib | ||
brmake | ||
check-package | ||
check-symbols | ||
config | ||
diffconfig | ||
docker-run | ||
genrandconfig | ||
get-developers | ||
getdeveloperlib.py | ||
readme.txt | ||
scancpan | ||
scanpypi | ||
size-stats-compare | ||
test-pkg |
This directory contains various useful scripts and tools for working with Buildroot. You need not add this directory in your PATH to use any of those tools, but you may do so if you want. brmake a script that can be run instead of make, that prepends the date in front of each line, redirects all of the build output to a file ("'br.log' in the current directory), and just outputs the Buildroot messages (those lines starting with >>>) on stdout. Do not run this script for interactive configuration (e.g. menuconfig) or on an unconfigured directory. The output is redirected so you will see nothing. check-package a script that checks the coding style of a package's Config.in and .mk files, and also tests them for various types of typoes. genrandconfig a script that generates a random configuration, used by the autobuilders (http://autobuild.buildroot.org). It selects a random toolchain from support/config-fragments/autobuild and randomly selects packages to build. get-developers a script to return the list of people interested in a specific part of Buildroot, so they can be Cc:ed on a mail. Accepts a patch as input, a package name or and architecture name. scancpan a script to create a Buildroot package by scanning a CPAN module description. scanpypi a script to create a Buildroot package by scanning a PyPI package description. size-stats-compare a script to compare the rootfs size between two different Buildroot configurations. This can be used to identify the size impact of a specific option, of a set of specific options, or of an update to a newer Buildroot version... test-pkg a script that tests a specific package against a set of various toolchains, with the goal to detect toolchain-related dependencies (wchar, threads...)