Take the vita-makepkg that finds the package client

vita-makepkg bbd1b18 stops defaulting PACMAN to $VITASDK/bin/pacman,
which is not where the client is: vdpm installs it at
libexec/vdpm/pacman, deliberately off PATH so a Linux distribution's own
pacman stays reachable as plain "pacman". Nothing here hit it, because
the core build hands vita-makepkg a PACMAN of its own -- but a recipe
built by hand against an installed SDK did not.

Its sibling commit fixes a test that had been failing on that repository
since 32f863c, silently: a bare grep under set -e, exit 1 having printed
nothing. The assertions still spelled out the --noscriptlet that
32f863c stopped passing on queries.

The pin stays untracked in cmake/pin-tracking.json: what changes here is
packaging behaviour the core package depends on, so it moves when
somebody has read it, which is now.

Author: frangarcj

cmake/Components.cmake

@@ -75,4 +75,4 @@ set(HEADERS_TAG 4f9b5d712751afef804a44d1d248ab2b358cff4a CACHE STRING "vita-head
 set(TOOLCHAIN_TAG eacff34d18e9872a78c0e520e1997ef71900ebb4 CACHE STRING "vita-toolchain branch, commit id or tag")
 set(PTHREAD_TAG 11d2e5722d98c86f33c908fc47b2cf6e55205db5 CACHE STRING "pthread-embedded branch, commit id or tag")
 set(VDPM_TAG v0.1.3 CACHE STRING "vdpm branch, commit id or tag")
-set(VITA_MAKEPKG_TAG 32f863c2a58a801b7d5a0296bdbbb443c9676e08 CACHE STRING "vita-makepkg branch, commit id or tag")
+set(VITA_MAKEPKG_TAG bbd1b18731cf8b6a69a18c9acdefd79a5b8c36eb CACHE STRING "vita-makepkg branch, commit id or tag")