FS#14727 - makepkg need to source ./PKGBUILD and not PKGBUILD only

Attached to Project: Pacman
Opened by RicardoH (richer) - Saturday, 16 May 2009, 02:33 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 19 May 2009, 04:44 GMT
Task Type Bug Report
Category makepkg
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version 3.2.2
Due in Version 3.3.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

makepkg source PKGBUILD and not ./PKGBUILD, that cause a problem, at least in one case escenario.

I have in my PATH ~/Scripts/ directory, and in Scripts i have a generic PKGBUILD. When i go to another directory with an specific PKGBUILD, say ~/foobar/PKGBUILD, and execute makepkg, it throws me an error: that pkgname must not be empty, because is reading the PKGBUILD from the PATH and not from the current directory.


Additional info:
* package version(s)

pacman 3.2.2-1 (makepkg tool)

* config and/or log files etc.

Steps to reproduce:

# cp /usr/share/pacman/PKGBUILD.proto ~/Scripts/PKGBUILD
# export PATH=$PATH:/home/user/Scripts
# cp ~/Scripts/PKGBUILD ~/foobar
# cd foobar
# (edit the PKGBUILD)
# makepkg
# ERROR
This task depends upon

Closed by  Dan McGee (toofishes)
Tuesday, 19 May 2009, 04:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  Commit 250e66e57b6a187b5643ea6db088552e4efef488
Comment by RicardoH (richer) - Saturday, 16 May 2009, 02:44 GMT
Thanks Allan, indeed is a bug report, i notice it later
Comment by Allan McRae (Allan) - Saturday, 16 May 2009, 03:58 GMT
Patch sent:
http://www.archlinux.org/pipermail/pacman-dev/2009-May/008657.html

Loading...