summaryrefslogtreecommitdiffstats
path: root/scripts/pacman-db-upgrade.sh.in
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2020-01-16 18:27:34 +0100
committerAndrew Gregory <andrew@archlinux.org>2020-06-18 10:43:04 +0200
commit0bf4779cda35cfb8dc049ec5f27017c65c8ce716 (patch)
treea00cb3213239467e770fc9354870951daaba66fc /scripts/pacman-db-upgrade.sh.in
parentd61c398b2cb3ec41e62a6e258b5791d0ce9de720 (diff)
downloadpacman-0bf4779cda35cfb8dc049ec5f27017c65c8ce716.tar.gz
pacman-0bf4779cda35cfb8dc049ec5f27017c65c8ce716.tar.xz
makepkg: make per-package files containing '$pkgname' consistently work
Extracting function variables containing arbitrarily scoped variables of arbitrary nature is a disaster, but let's at least cover the common case of using the actual '$pkgname' in an install/changelog file. It's the odd case of actually being basically justified use of disambiguating between the same variable used in multiple different split packages... and also, --printsrcinfo already uses and overwrites the variable 'pkgname' in pkgbuild_extract_to_srcinfo, so this "works" in .SRCINFO but doesn't work in .src.tar.gz It doesn't work in lint_pkgbuild either, but in that case the problem is being too permissive, not too restrictive -- we might end up checking the same file twice, and printing that it is missing twice. Fixes FS#64932 Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org> (cherry picked from commit d626a17ef94d79975ff17d04250152ea46aaade3)
Diffstat (limited to 'scripts/pacman-db-upgrade.sh.in')
0 files changed, 0 insertions, 0 deletions