summaryrefslogtreecommitdiffstats
path: root/scripts/libmakepkg/lint_pkgbuild/package_function.sh.in
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2019-05-22 16:44:26 +0200
committerAllan McRae <allan@archlinux.org>2019-05-28 03:28:30 +0200
commita00615bfdad628299352b94e0f44d211a758fd17 (patch)
tree6ac7380ccbdbfd0dfc64493e2d025952df133e6e /scripts/libmakepkg/lint_pkgbuild/package_function.sh.in
parent5caf45cdbb267ee45c7b4a9c815e500efd350e6e (diff)
downloadpacman-a00615bfdad628299352b94e0f44d211a758fd17.tar.gz
pacman-a00615bfdad628299352b94e0f44d211a758fd17.tar.xz
makepkg: move config loading into libmakepkg
When scripting/automating around makepkg, it is sometimes desirable to know how makepkg will be configured to operate. One example is the archlinux devtools, which must forward select makepkg.conf variables into a build chroot (for example PACKAGER) or use those variables itself (for example {SRC,PKG,LOG}DEST). The configuration file can be in up to 3 places, and should be capable of being overridden via environment variables. It is sufficiently complex to represent distinct functionality, and sufficiently useful to merit easy accessibility in other scripts, therefore, let us move it into a publicly exposed utility library. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'scripts/libmakepkg/lint_pkgbuild/package_function.sh.in')
0 files changed, 0 insertions, 0 deletions