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> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .checkpackageignore | ||
| .clang-format | ||
| .defconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .shellcheckrc | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches