Leo Famulari <l...@famulari.name> writes: > On Tue, Jan 24, 2017 at 03:40:13PM +0100, Ricardo Wurmus wrote: >> * gnu/packages/lua.scm (lua5.2-bitop): New variable. > >> + (arguments >> + `(#:test-target "test" >> + #:make-flags >> + (list "INSTALL=install -pD" >> + (string-append "INSTALLPATH=printf " > > What's up with this "printf"? Does it actually execute the value of > INSTALLPATH?
INSTALLPATH defaults to “lua somefile.lua”, and it is applied to the name of the module (“bit”). If I just changed INSTALLPATH to a literal path, the “install” target would try to execute it with “bit” as an argument. This is why I’m using “printf”, which when given a string literal ignores any other arguments. The result is just the install path. I chose this method over patching the Makefile. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
