choose newest extension source

Some extensions authors introduce build steps required before
installing. Their execution normally produces a completed variant of the
extension code in a subdirectory, difficult to tell apart from the
original source. The find condition introduced herein proves the process
against such cases to come. It always chooses the files created last,
ensuring that a build which occurred after mere unpacking will always
take precedence.

1 files changed, 2 insertions, 1 deletions

diff --git a/PKGBUILD b/PKGBUILD
index dea18d43a78b..c6f958e6988e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -53,7 +53,8 @@ package() {
 }
 package_01_locate() {
   msg2 'Locating extension...'
-  cd "$(find -name 'metadata.json' -execdir test -e extension.js \; -printf %h -quit)"
+  cd "$(find -name 'metadata.json' -execdir test -e extension.js \; \
+    -printf '%C@ %h\n' | sort -nr | sed 's/^.* //;q' )"
   extname=$(grep -Po '(?<="uuid": ")[^"]*' metadata.json)
   destdir="$pkgdir/usr/share/gnome-shell/extensions/$extname"
 }