Allan McRae 2401468f51 makepkg: Force buildscripts to be in startdir ... We expect all source file to lie in $startdir. However, using "makepkg -p <buildscript>" can currently allows people to specify buildscripts in other directories. This results in confusion about where other sources should lie (in startdir or in the directory that the buildscript is in). Explicitly disable using -p for files in other directories to avoid this issue. Fixes FS#40293. Signed-off-by: Allan McRae <allan@archlinux.org>		2014-05-25 13:53:19 +10:00
..
library	Consistently use 'directory' instead of 'folder'	2014-01-28 21:37:00 +10:00
po	Do not remove source code references in PO/POT files	2014-02-02 16:32:55 +10:00
.gitignore	makepkg: run locally with libtool style wrapper	2013-10-14 13:01:03 +10:00
Makefile.am	Do not check makepkg-wrapper for standard options	2014-05-23 16:02:18 +10:00
makepkg-template.pl.in	Update copyright years for 2014	2014-01-06 14:38:50 +10:00
makepkg-wrapper.sh.in	Update copyright years for 2014	2014-01-06 14:38:50 +10:00
makepkg.sh.in	makepkg: Force buildscripts to be in startdir	2014-05-25 13:53:19 +10:00
pacman-db-upgrade.sh.in	Remove ts and sw from vim modeline when noet is set	2014-01-28 20:19:25 +10:00
pacman-key.sh.in	Remove ts and sw from vim modeline when noet is set	2014-01-28 20:19:25 +10:00
pacman-optimize.sh.in	Remove ts and sw from vim modeline when noet is set	2014-01-28 20:19:25 +10:00
pkgdelta.sh.in	Remove ts and sw from vim modeline when noet is set	2014-01-28 20:19:25 +10:00
repo-add.sh.in	repo-add: declare pkgbase as local	2014-03-27 15:46:07 +10:00