Don't attempt symlinking a community patch when it exists in the userpatches dir (else the userpatch gets eaten away by ln failing to symlink, leaving you with nothing).

And throw a warning about it for good measure.
This commit is contained in:
Tk-Glitch
2022-06-13 18:13:53 +02:00
parent 0dbf0095f1
commit 9620363ed1

View File

@@ -1368,7 +1368,11 @@ CONFIG_DEBUG_INFO_BTF_MODULES=y\r
_community_patches=($_community_patches) _community_patches=($_community_patches)
mkdir -p "$_where"/linux"$_basever"-tkg-userpatches mkdir -p "$_where"/linux"$_basever"-tkg-userpatches
for _p in ${_community_patches[@]}; do for _p in ${_community_patches[@]}; do
if [ ! -e "$_where/linux$_basever-tkg-userpatches/$_p" ]; then
ln -s "$_where"/../community-patches/linux"$_basever"-tkg/$_p "$_where"/linux"$_basever"-tkg-userpatches/$_p ln -s "$_where"/../community-patches/linux"$_basever"-tkg/$_p "$_where"/linux"$_basever"-tkg-userpatches/$_p
else
warning "Ignoring '$_p' community patch already present in the userpatches dir"
fi
done done
fi fi