Arch Linux User Repository

Thanks @NextAlone for the comment. I opted to create explicit variables for major, minor and micro version numbers instead of your suggestion 👍

Something wrong with dest dir, r33.0.1 installed into /opt/android-sdk/build-tools/33.0.1.0.0, and version is detected as 0.0.0, so changes are below, may this be reviewed and fixed.

diff --git a/PKGBUILD b/PKGBUILD
index 5a32dda..7576c65 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -26,12 +26,12 @@ package() {
   cd "$pkgdir"

   install -d usr/share/licenses/$pkgname/
-  ln -s /opt/$_sdk/build-tools/$_ver.0.0/NOTICE.txt usr/share/licenses/$pkgname/NOTICE.txt
-  sed -i "s/@major@/$_ver/g;s/@minor@/0/g;s/@micro@/0/g" "$srcdir/package.xml"
-  install -Dm644 "${srcdir}/package.xml" opt/$_sdk/build-tools/$_ver.0.0/package.xml
-  ln -s /opt/$_sdk/build-tools/$_ver.0.0/package.xml usr/share/licenses/$pkgname/package.xml
+  ln -s /opt/$_sdk/build-tools/$_ver/NOTICE.txt usr/share/licenses/$pkgname/NOTICE.txt
+  sed -i "s/@major@/${_ver:0:0-4}/g;s/@minor@/${_ver:0-3:1}/g;s/@micro@/${_ver:0-1:1}/g" "$srcdir/package.xml"
+  install -Dm644 "${srcdir}/package.xml" opt/$_sdk/build-tools/$_ver/package.xml
+  ln -s /opt/$_sdk/build-tools/$_ver/package.xml usr/share/licenses/$pkgname/package.xml

-  target="opt/$_sdk/build-tools/$_ver.0.0"
+  target="opt/$_sdk/build-tools/$_ver"
   mkdir -p "$target"
   cp -r "$srcdir/$_android/"* "$target"
   chmod +Xr -R "$target"

I use Quasar with cordova which allows to put an application on mobile, cordova uses android-sdk-build-tools, when I launch the build it gives me a message that I had not signed the packages! but i finally found the problem. the command line signs in the wrong place! you had to move the signatures for cordova to detect them!

Sorry for not updating my post! I hope this can help someone else!

@Floriantoine: Can you provide more information/error messages?

I don't sign AUR packages, but I can't imagine a reason why this particular package would have problems being signed. Maybe check with the documentation how to sign packages again?

Is still impossible for me to sign the package, I place the order the return tells me that everything is well signed, yet nothing concerning this package... a solution ?

Hi @gnaggnoyil, android-sdk-build-tools does contain d8 and some other executables. They are stored in a directory with non-executables, so adding it to the PATH is problematic. Thus I created the symlinks.

I made an exception for lld, which is a package in the official repos. I do not intend to add another exception for an AUR package. The question is: what happens when you manually remove the symlink or install v8-r with pacman -U --overwrite /usr/bin/d8 [pkg]?

This package has conflicting file usr/bin/d8 with the aur/v8-r package. Is there any way to resolve this file conflict error? FYI, usr/bin/d8 in v8-r package is an actual executable instead of a symlink.

Package doesn't provide dx - description should be updated and broken /usr/bin/dx link should be removed

@acer189 That's expected. I included the package.xml in the package, so you don't have to accept the license in Android Studio.

Unfortunately an update to the current version did not work for me. The error message:

Error: The operation could not be performed (Conflicting files) android-sdk-build-tools: /opt/android-sdk/build-tools/32.0.0/package.xml exists in the >file system Errors occurred, no packages were updated.