RFC: Replace absolute path to git-tree with relative

[adeepn]

Description

Replace absolute path to git-tree with relative, so it is accesible without docker builder.

was:

$ cat cache/sources/linux-kernel-worktree/6.2__jethome64__arm64/.git
gitdir: /armbian/cache/git-bare/kernel/.git/worktrees/6.2__jethome64__arm64

new:

$ cat cache/sources/linux-kernel-worktree/6.2__jethome64__arm64/.git
gitdir: ../../../git-bare/kernel/.git/worktrees/6.2__jethome64__arm64

Jira reference number [AR-9999]

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• Build ok
• Access to git tree without docker builder ok

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[iav]

What need to be run to see an error you fix there?

[adeepn]

What need to be run to see an error you fix there?

this is QoL update.
with this changes you can access git tree of kernel/uboot sources inside cache dir without run docker armbian-builder if main build processed inside docker
it does not change anything in the build process

[iav]

On my system folder cache/sources/linux-kernel-worktree/6.1__rockchip64__arm64 have .github folder, but not have .git.
Hm?

[adeepn]

On my system folder cache/sources/linux-kernel-worktree/6.1__rockchip64__arm64 have .github folder, but not have .git. Hm?

.git is file, not dir

[iav]

It works!

[rpardini]

Nice, I had the absolute in there to fix some problem reported early in the -next testing cycle (gotta find git blame)

One consideration about the concept:

• Sharing the git tree in-Docker and out-of-Docker only really works well if both host and Docker are on the same OS (Linux) and git binary is somewhat the same version.... otherwise git has to refresh the index constantly. Happens on macOS for example, or with large "gaps" in git version (bulleye's vs kinetic's for example)

About the implementation:

• maybe consider coreutil's realpath --relative-to instead of sed magic? (or... not. I dunno)

[adeepn]

• maybe consider coreutil's realpath --relative-to instead of sed magic? (or... not. I dunno)

damn. of course, it's so much easier)