[arch-general] PKGBUILD weirdness

Jan Alexander Steffens jan.steffens at gmail.com
Thu Apr 11 09:51:39 EDT 2013

On Thu, Apr 11, 2013 at 3:43 PM, Robbie Smith <zoqaeski at gmail.com> wrote:
> On 11/04/13 22:20, Jan Alexander Steffens wrote:
>> On Thu, Apr 11, 2013 at 1:16 PM, Robbie Smith <zoqaeski at gmail.com> wrote:
>>> I’ve been working on my own fork of luakit, building and installing it to
>>> test changes, and I’ve come across some weirdness in the PKGBUILD. The
>>> original luakit-git PKGBUILD[1] has a set of options to pass to make to
>>> (for
>>> example) enable luajit.
>>> I rewrote it to conform with pacman/makepkg 4.1 vcs standards[2], and for
>>> some reason, if I use an auxiliary variable to store these options, the
>>> packaging fails. Can anyone shed some light on why this might be so?
>>> [1] https://aur.archlinux.org/packages/lu/luakit-git/PKGBUILD
>>> [2] https://github.com/luakit-crowd/luakit/blob/develop/extras/PKGBUILD
>> Because $pkgdir only exists in the package() function. Using it
>> earlier won't work.
> OK…
> So why does the $_makeopts variable work in build() but not in package(),
> even if I drop $pkgdir from it? It should either work for both or fail for
> both if there’s no reference to $pkgdir, shouldn’t it?

Missing variables are replaced with nothing instead of immediately
causing an error, and DESTDIR is not used during build.

More information about the arch-general mailing list