FS#41862 - [pacman-git] noextract option in PKGBUILD doesn't symlink file into ${srcdir}
Attached to Project:
Pacman
Opened by need to rename username but can't, guess I'll create a new one then (m4cz3) - Sunday, 07 September 2014, 18:16 GMT
Last edited by Allan McRae (Allan) - Wednesday, 19 November 2014, 06:16 GMT
Opened by need to rename username but can't, guess I'll create a new one then (m4cz3) - Sunday, 07 September 2014, 18:16 GMT
Last edited by Allan McRae (Allan) - Wednesday, 19 November 2014, 06:16 GMT
|
Details
Description:
Looks like noextract option inside PKGBUILD prevents that file from being softlinked into ${srcdir} and thus the need to use ${SRCDEST} to access it. As an example of this try chromium-dev package. Without noextract it is symlinked, with noextract it isn't. Maybe this is a feature? Additional info: * package version(s) with pacman(package) it works correctly though. With pacman-git(package) doesn't. pacman-git version currently is: Tested with: Pacman v4.1.2-406-g3e19-dirty - libalpm v8.0.2 * config and/or log files etc. tested with pacman(package)'s makepkg.conf and pacman.conf and also with my own. Steps to reproduce: 1. yaourt -S chromium-dev 2. put echo `pwd` ls -la at the beginning of prepare function 3. proceed with build, notice it fails soon after downloading that 200+ MB file commenting out the noextract= line will symlink and also extract that tar.xz file |
makepkg.conf
This task depends upon
Closed by Allan McRae (Allan)
Wednesday, 19 November 2014, 06:16 GMT
Reason for closing: Fixed
Additional comments about closing: git commit a7298c36fdc5
Wednesday, 19 November 2014, 06:16 GMT
Reason for closing: Fixed
Additional comments about closing: git commit a7298c36fdc5
Do NOT report bugs when a package is ... in Unsupported
pacman-git fits that category