[pacman-dev] [PATCH 1/5] Add warning in PKGBUILD manpage about use of $startdir/{src, pkg}
Signed-off-by: Sebastien Luttringer <seblu@seblu.net> --- doc/PKGBUILD.5.txt | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index af3a388..eeea4da 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -273,6 +273,8 @@ variables for use during the build and install process: *startdir*:: This contains the absolute path to the directory where the PKGBUILD is located, which is usually the output of `$(pwd)` when makepkg is started. + `$startdir/src` is not guaranteed to be the same as `$srcdir`, and likewise + for `$pkgdir`. *srcdir*:: This contains the directory where makepkg extracts, or copies, all source -- Sebastien "Seblu" Luttringer
Signed-off-by: Sebastien Luttringer <seblu@seblu.net> --- scripts/makepkg.sh.in | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 8845a41..fa12702 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -439,8 +439,7 @@ check_deps() { local ret=0 local pmout pmout=$(run_pacman -T "$@") || ret=$? - set -E - + set -E if (( ret == 127 )); then #unresolved deps echo "$pmout" elif (( ret )); then -- Sebastien "Seblu" Luttringer
On 09/08/11 20:56, Sebastien Luttringer wrote:
Signed-off-by: Sebastien Luttringer<seblu@seblu.net> --- scripts/makepkg.sh.in | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 8845a41..fa12702 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -439,8 +439,7 @@ check_deps() { local ret=0 local pmout pmout=$(run_pacman -T "$@") || ret=$? - set -E - + set -E if (( ret == 127 )); then #unresolved deps echo "$pmout" elif (( ret )); then
I'd like the newline kept.
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail. Signed-off-by: Sebastien Luttringer <seblu@seblu.net> --- scripts/makepkg.sh.in | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index fa12702..05880b7 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -134,10 +134,10 @@ clean_up() { return fi - if (( ! EXIT_CODE && CLEANUP )); then + if (( CLEANUP )); then local pkg file - # If it's a clean exit and -c/--clean has been passed... + # Cleaning if -c/--clean has been passed... msg "$(gettext "Cleaning up...")" rm -rf "$pkgdir" "$srcdir" if [[ -n $pkgbase ]]; then -- Sebastien "Seblu" Luttringer
On Tue, Aug 09, 2011 at 12:56:41PM +0200, Sebastien Luttringer wrote:
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail.
I think this is intended behavior. One might want to investigate _why_ a build failed by looking in the $srcdir. dave
Signed-off-by: Sebastien Luttringer <seblu@seblu.net> --- scripts/makepkg.sh.in | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index fa12702..05880b7 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -134,10 +134,10 @@ clean_up() { return fi
- if (( ! EXIT_CODE && CLEANUP )); then + if (( CLEANUP )); then local pkg file
- # If it's a clean exit and -c/--clean has been passed... + # Cleaning if -c/--clean has been passed... msg "$(gettext "Cleaning up...")" rm -rf "$pkgdir" "$srcdir" if [[ -n $pkgbase ]]; then -- Sebastien "Seblu" Luttringer
On Fri, Aug 12, 2011 at 6:58 PM, Dave Reisner <d@falconindy.com> wrote:
On Tue, Aug 09, 2011 at 12:56:41PM +0200, Sebastien Luttringer wrote:
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail.
I think this is intended behavior. One might want to investigate _why_ a build failed by looking in the $srcdir. Someone who wants to investigate a build failure doesn't pass -c as argument ?
Same as you don't strip when you want to debug. gcc -g toto.c -o toto; strip toto, have the same behaviour When you call "makepkg", it will fail and don't remove content to make investigation. If you call "makepkg -c", i suppose, you want do clean (even it fail). My idea was to be able to clean a directory without build package. But i can implement something like -C which just clean content of the current directory. -- Sébastien Luttringer www.seblu.net
On Fri, Aug 12, 2011 at 07:49:07PM +0200, Seblu wrote:
On Fri, Aug 12, 2011 at 6:58 PM, Dave Reisner <d@falconindy.com> wrote:
On Tue, Aug 09, 2011 at 12:56:41PM +0200, Sebastien Luttringer wrote:
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail.
I think this is intended behavior. One might want to investigate _why_ a build failed by looking in the $srcdir. Someone who wants to investigate a build failure doesn't pass -c as argument ?
You're assuming that you know beforehand that the package will build correctly. For any non-vcs package, I almost always want to use `makepkg -risc'.
Same as you don't strip when you want to debug. gcc -g toto.c -o toto; strip toto, have the same behaviour
I don't think how this is analogous. The behavior we have with -c is more similar to: make && make install && make clean Note the conditional nature of this.
When you call "makepkg", it will fail and don't remove content to make investigation. If you call "makepkg -c", i suppose, you want do clean (even it fail).
And as I mentioned above, you don't know that the package will be built successfully, but you want the build directory cleaned IFF it does build.
My idea was to be able to clean a directory without build package. But i can implement something like -C which just clean content of the current directory.
On Fri, Aug 12, 2011 at 8:06 PM, Dave Reisner <d@falconindy.com> wrote:
On Fri, Aug 12, 2011 at 07:49:07PM +0200, Seblu wrote:
On Fri, Aug 12, 2011 at 6:58 PM, Dave Reisner <d@falconindy.com> wrote:
On Tue, Aug 09, 2011 at 12:56:41PM +0200, Sebastien Luttringer wrote:
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail.
I think this is intended behavior. One might want to investigate _why_ a build failed by looking in the $srcdir. Someone who wants to investigate a build failure doesn't pass -c as argument ?
You're assuming that you know beforehand that the package will build correctly. For any non-vcs package, I almost always want to use `makepkg -risc'.
Same as you don't strip when you want to debug. gcc -g toto.c -o toto; strip toto, have the same behaviour
I don't think how this is analogous. The behavior we have with -c is more similar to:
make && make install && make clean
Note the conditional nature of this.
When you call "makepkg", it will fail and don't remove content to make investigation. If you call "makepkg -c", i suppose, you want do clean (even it fail).
And as I mentioned above, you don't know that the package will be built successfully, but you want the build directory cleaned IFF it does build. ok do you think a -C which clean inconditionnaly and let -c clean when success ?
Regards, -- Sébastien Luttringer www.seblu.net
On 13/08/11 04:34, Seblu wrote:
On Fri, Aug 12, 2011 at 8:06 PM, Dave Reisner<d@falconindy.com> wrote:
On Fri, Aug 12, 2011 at 07:49:07PM +0200, Seblu wrote:
On Fri, Aug 12, 2011 at 6:58 PM, Dave Reisner<d@falconindy.com> wrote:
On Tue, Aug 09, 2011 at 12:56:41PM +0200, Sebastien Luttringer wrote:
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail.
I think this is intended behavior. One might want to investigate _why_ a build failed by looking in the $srcdir. Someone who wants to investigate a build failure doesn't pass -c as argument ?
You're assuming that you know beforehand that the package will build correctly. For any non-vcs package, I almost always want to use `makepkg -risc'.
Same as you don't strip when you want to debug. gcc -g toto.c -o toto; strip toto, have the same behaviour
I don't think how this is analogous. The behavior we have with -c is more similar to:
make&& make install&& make clean
Note the conditional nature of this.
When you call "makepkg", it will fail and don't remove content to make investigation. If you call "makepkg -c", i suppose, you want do clean (even it fail).
And as I mentioned above, you don't know that the package will be built successfully, but you want the build directory cleaned IFF it does build. ok do you think a -C which clean inconditionnaly and let -c clean when success ?
Is it really necessary? "rm -rf pkg/ src/" does the job... Allan
On Sat, Aug 13, 2011 at 12:53 AM, Allan McRae <allan@archlinux.org> wrote:
On 13/08/11 04:34, Seblu wrote:
On Fri, Aug 12, 2011 at 8:06 PM, Dave Reisner<d@falconindy.com> wrote:
On Fri, Aug 12, 2011 at 07:49:07PM +0200, Seblu wrote:
On Fri, Aug 12, 2011 at 6:58 PM, Dave Reisner<d@falconindy.com> wrote:
On Tue, Aug 09, 2011 at 12:56:41PM +0200, Sebastien Luttringer wrote:
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail.
I think this is intended behavior. One might want to investigate _why_ a build failed by looking in the $srcdir.
Someone who wants to investigate a build failure doesn't pass -c as argument ?
You're assuming that you know beforehand that the package will build correctly. For any non-vcs package, I almost always want to use `makepkg -risc'.
Same as you don't strip when you want to debug. gcc -g toto.c -o toto; strip toto, have the same behaviour
I don't think how this is analogous. The behavior we have with -c is more similar to:
make&& make install&& make clean
Note the conditional nature of this.
When you call "makepkg", it will fail and don't remove content to make investigation. If you call "makepkg -c", i suppose, you want do clean (even it fail).
And as I mentioned above, you don't know that the package will be built successfully, but you want the build directory cleaned IFF it does build.
ok do you think a -C which clean inconditionnaly and let -c clean when success ?
Is it really necessary? "rm -rf pkg/ src/" does the job...
ok -- Sébastien Luttringer www.seblu.net
On Sat, Aug 13, 2011 at 1:08 AM, Seblu <seblu@seblu.net> wrote:
On Sat, Aug 13, 2011 at 12:53 AM, Allan McRae <allan@archlinux.org> wrote:
Is it really necessary? "rm -rf pkg/ src/" does the job...
ok
I have these functions in my .bashrc. Feel free to use or modify them. cdp() { local relpath="$HOME/abs" subdirs if ! [[ "$PWD" == "$relpath"* ]]; then echo "Error: this function is made for use in $relpath" >&2 return 1 fi subdirs="${PWD:${#relpath}+1}" cd "$relpath/${subdirs%%/*}" } nanop() { if cdp; then set -- -Ysh "PKGBUILD" $(which nano) "$@" cd - fi } clearp() { if cdp; then . /etc/makepkg.conf rm -rf src pkg *"$PKGEXT" *"$SRCEXT" fi }
On Tue, Aug 09, 2011 at 12:56:41PM +0200, Sebastien Luttringer wrote:
Before this, cleaning is done when script exit with a value != 0. If a build fail, directory remain unclean. The purpose of cleaning should not be changed if build fail.
Signed-off-by: Sebastien Luttringer <seblu@seblu.net> --- scripts/makepkg.sh.in | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
-1. The purpose of this is to be able to analyze the build directory in case of a build failure which makes it easier to spot and backtrack any errors.
diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index fa12702..05880b7 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -134,10 +134,10 @@ clean_up() { return fi
- if (( ! EXIT_CODE && CLEANUP )); then + if (( CLEANUP )); then local pkg file
- # If it's a clean exit and -c/--clean has been passed... + # Cleaning if -c/--clean has been passed... msg "$(gettext "Cleaning up...")" rm -rf "$pkgdir" "$srcdir" if [[ -n $pkgbase ]]; then -- Sebastien "Seblu" Luttringer
makepkg --source is a often used go make source package like for AUR. Have a -S shortcut will save the world. Signed-off-by: Sebastien Luttringer <seblu@seblu.net> --- contrib/bash_completion.in | 2 +- scripts/makepkg.sh.in | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/contrib/bash_completion.in b/contrib/bash_completion.in index af5de17..8fa3da6 100644 --- a/contrib/bash_completion.in +++ b/contrib/bash_completion.in @@ -35,7 +35,7 @@ _makepkg() { opts=('allsource asroot check clean config force geninteg help holdver ignorearch install log nobuild nocheck nocolor noconfirm nodeps noextract noprogressbar nosign pkg repackage rmdeps sign skipinteg source syncdeps' - 'A L R c d e f g h i m o p r s') + 'A L R S c d e f g h i m o p r s') _arch_ptr2comp opts fi true diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 05880b7..0121f77 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -1843,6 +1843,7 @@ usage() { echo "$(gettext " -r, --rmdeps Remove installed dependencies after a successful build")" echo "$(gettext " -R, --repackage Repackage contents of the package without rebuilding")" printf "$(gettext " -s, --syncdeps Install missing dependencies with %s")\n" "pacman" + echo "$(gettext " -S, --source Generate a source-only tarball without downloaded sources")" echo "$(gettext " --allsource Generate a source-only tarball including downloaded sources")" printf "$(gettext " --asroot Allow %s to run as root user")\n" "makepkg" printf "$(gettext " --check Run the %s function in the %s")\n" "check()" "$BUILDSCRIPT" @@ -1856,7 +1857,6 @@ usage() { echo "$(gettext " --skipchecksums Do not verify checksums of the source files")" echo "$(gettext " --skipinteg Do not perform any verification checks on source files")" echo "$(gettext " --skippgpcheck Do not verify source files with PGP signatures")" - echo "$(gettext " --source Generate a source-only tarball without downloaded sources")" echo printf "$(gettext "These options can be passed to %s:")\n" "pacman" echo @@ -1888,7 +1888,7 @@ fi ARGLIST=("$@") # Parse Command Line Options. -OPT_SHORT="AcdefFghiLmop:rRsV" +OPT_SHORT="AcdefFghiLmop:rRsSV" OPT_LONG="allsource,asroot,ignorearch,check,clean,nodeps" OPT_LONG+=",noextract,force,forcever:,geninteg,help,holdver,skippgpcheck" OPT_LONG+=",install,key:,log,nocolor,nobuild,nocheck,nosign,pkg:,rmdeps" @@ -1939,8 +1939,8 @@ while true; do --skipinteg) SKIPCHECKSUMS=1; SKIPPGPCHECK=1 ;; --skippgpcheck) SKIPPGPCHECK=1;; --sign) SIGNPKG='y' ;; - --source) SOURCEONLY=1 ;; -s|--syncdeps) DEP_BIN=1 ;; + -S|--source) SOURCEONLY=1 ;; -h|--help) usage; exit 0 ;; # E_OK -V|--version) version; exit 0 ;; # E_OK -- Sebastien "Seblu" Luttringer
makepkg --skipinteg is a often used to test package and it's the brother of -g option. Have a -G shortcut will help to reduce CO². Signed-off-by: Sebastien Luttringer <seblu@seblu.net> --- contrib/bash_completion.in | 2 +- scripts/makepkg.sh.in | 8 ++++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/contrib/bash_completion.in b/contrib/bash_completion.in index 8fa3da6..79a5154 100644 --- a/contrib/bash_completion.in +++ b/contrib/bash_completion.in @@ -35,7 +35,7 @@ _makepkg() { opts=('allsource asroot check clean config force geninteg help holdver ignorearch install log nobuild nocheck nocolor noconfirm nodeps noextract noprogressbar nosign pkg repackage rmdeps sign skipinteg source syncdeps' - 'A L R S c d e f g h i m o p r s') + 'A G L R S c d e f g h i m o p r s') _arch_ptr2comp opts fi true diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 0121f77..4a17999 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -1834,6 +1834,7 @@ usage() { printf "$(gettext " -e, --noextract Do not extract source files (use existing %s dir)")\n" "src/" echo "$(gettext " -f, --force Overwrite existing package")" echo "$(gettext " -g, --geninteg Generate integrity checks for source files")" + echo "$(gettext " -G, --skipinteg Do not fail when integrity checks are missing")" echo "$(gettext " -h, --help Show this help message and exit")" echo "$(gettext " -i, --install Install package after successful build")" echo "$(gettext " -L, --log Log package build process")" @@ -1855,7 +1856,6 @@ usage() { echo "$(gettext " --pkg <list> Only build listed packages from a split package")" printf "$(gettext " --sign Sign the resulting package with %s")\n" "gpg" echo "$(gettext " --skipchecksums Do not verify checksums of the source files")" - echo "$(gettext " --skipinteg Do not perform any verification checks on source files")" echo "$(gettext " --skippgpcheck Do not verify source files with PGP signatures")" echo printf "$(gettext "These options can be passed to %s:")\n" "pacman" @@ -1888,7 +1888,7 @@ fi ARGLIST=("$@") # Parse Command Line Options. -OPT_SHORT="AcdefFghiLmop:rRsSV" +OPT_SHORT="AcdefFgGhiLmop:rRsSV" OPT_LONG="allsource,asroot,ignorearch,check,clean,nodeps" OPT_LONG+=",noextract,force,forcever:,geninteg,help,holdver,skippgpcheck" OPT_LONG+=",install,key:,log,nocolor,nobuild,nocheck,nosign,pkg:,rmdeps" @@ -1923,6 +1923,7 @@ while true; do --forcever) shift; FORCE_VER=$1;; -F) INFAKEROOT=1 ;; -g|--geninteg) GENINTEG=1 ;; + -G|--skipinteg) SKIPINTEG=1 ;; --holdver) HOLDVER=1 ;; -i|--install) INSTALL=1 ;; --key) shift; GPGKEY=$1 ;; @@ -1935,9 +1936,12 @@ while true; do --pkg) shift; PKGLIST=($1) ;; -r|--rmdeps) RMDEPS=1 ;; -R|--repackage) REPKG=1 ;; +<<<<<<< HEAD --skipchecksums) SKIPCHECKSUMS=1 ;; --skipinteg) SKIPCHECKSUMS=1; SKIPPGPCHECK=1 ;; --skippgpcheck) SKIPPGPCHECK=1;; +======= +>>>>>>> Add makepkg -G which is like --skipinteg --sign) SIGNPKG='y' ;; -s|--syncdeps) DEP_BIN=1 ;; -S|--source) SOURCEONLY=1 ;; -- Sebastien "Seblu" Luttringer
On Tue, Aug 9, 2011 at 6:56 AM, Sebastien Luttringer <seblu@seblu.net> wrote:
makepkg --skipinteg is a often used to test package and it's the brother of -g option. Have a -G shortcut will help to reduce CO².
Signed-off-by: Sebastien Luttringer <seblu@seblu.net> ---
+<<<<<<< HEAD --skipchecksums) SKIPCHECKSUMS=1 ;; --skipinteg) SKIPCHECKSUMS=1; SKIPPGPCHECK=1 ;; --skippgpcheck) SKIPPGPCHECK=1;; +======= +>>>>>>> Add makepkg -G which is like --skipinteg --sign) SIGNPKG='y' ;; -s|--syncdeps) DEP_BIN=1 ;; -S|--source) SOURCEONLY=1 ;;
The patch seem to be messed up.
thanks Eric, i will correct this. On Fri, Aug 12, 2011 at 10:04 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Tue, Aug 9, 2011 at 6:56 AM, Sebastien Luttringer <seblu@seblu.net> wrote:
makepkg --skipinteg is a often used to test package and it's the brother of -g option. Have a -G shortcut will help to reduce CO².
Signed-off-by: Sebastien Luttringer <seblu@seblu.net> ---
+<<<<<<< HEAD --skipchecksums) SKIPCHECKSUMS=1 ;; --skipinteg) SKIPCHECKSUMS=1; SKIPPGPCHECK=1 ;; --skippgpcheck) SKIPPGPCHECK=1;; +======= +>>>>>>> Add makepkg -G which is like --skipinteg --sign) SIGNPKG='y' ;; -s|--syncdeps) DEP_BIN=1 ;; -S|--source) SOURCEONLY=1 ;;
The patch seem to be messed up.
-- Sébastien Luttringer www.seblu.net
On 09/08/11 20:56, Sebastien Luttringer wrote:
makepkg --skipinteg is a often used to test package and it's the brother of -g option. Have a -G shortcut will help to reduce CO².
Signed-off-by: Sebastien Luttringer<seblu@seblu.net>
This was somewhat deliberately done not to have a short option for this because --skipinteg was not intend to be used often. So I am undecided on this. And should -G be --skipinteg or just --skipchecksums?
On Sat, Aug 13, 2011 at 1:32 AM, Allan McRae <allan@archlinux.org> wrote:
On 09/08/11 20:56, Sebastien Luttringer wrote:
makepkg --skipinteg is a often used to test package and it's the brother of -g option. Have a -G shortcut will help to reduce CO².
Signed-off-by: Sebastien Luttringer<seblu@seblu.net>
This was somewhat deliberately done not to have a short option for this because --skipinteg was not intend to be used often. So I am undecided on this. I use --skipinteg when i build several version of the same package. With the new package signing, it can also be useful to be able to "quickly" escape signature verif.
Maybe i bad see the policy of short option in pacman, but almost all options should have a long and short form. Letting user choose with version he likes. Here i think it's a usefull option.
And should -G be --skipinteg or just --skipchecksums
I think everything which can fail build process, so --skipinteg. -- Sébastien Luttringer www.seblu.net
On Fri, Aug 12, 2011 at 6:32 PM, Allan McRae <allan@archlinux.org> wrote:
On 09/08/11 20:56, Sebastien Luttringer wrote:
makepkg --skipinteg is a often used to test package and it's the brother of -g option. Have a -G shortcut will help to reduce CO².
Signed-off-by: Sebastien Luttringer<seblu@seblu.net>
This was somewhat deliberately done not to have a short option for this because --skipinteg was not intend to be used often. So I am undecided on this.
I'm -1 for this reason. If you don't like typing --skipinteg (or hell, getting tab completion of `makepkg -sk<tab>`, you're being really lazy. I also see the -G option being spoon fed to users on IRC or the wiki without them realizing what it does; at least in the current situation the flag is slightly self-explanatory. You do realize you can do `makepkg -g >> PKGBUILD` over and over again, and having them defined multiple times in the PKGBUILD doesn't hurt anything during testing, right? Nor do you need to move them from the bottom for them to work... -Dan
On 09/08/11 20:56, Sebastien Luttringer wrote:
Signed-off-by: Sebastien Luttringer<seblu@seblu.net> --- doc/PKGBUILD.5.txt | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index af3a388..eeea4da 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -273,6 +273,8 @@ variables for use during the build and install process: *startdir*:: This contains the absolute path to the directory where the PKGBUILD is located, which is usually the output of `$(pwd)` when makepkg is started. + `$startdir/src` is not guaranteed to be the same as `$srcdir`, and likewise + for `$pkgdir`.
*srcdir*:: This contains the directory where makepkg extracts, or copies, all source
I'd prefer to add a warning that there is probably no reason to ever use $startdir in a PKGBUILD rather that mentioning constructs like $startdir/src which have been deprecated for years now. Allan
participants (8)
-
Allan McRae
-
Dan McGee
-
Dave Reisner
-
Eric Bélanger
-
Lukas Fleischer
-
Martti Kühne
-
Sebastien Luttringer
-
Seblu