[aur-general] Review and a bit of other help request

[Konstantin Gizdov]

Hi Uwe,

So I edited my /etc/makepkg.conf to have the following:
...
MAKEFLAGS="-j$(nproc)"
...

I assumed every time 'makepkg' is run, it would source it's environment and
that file as well. I am not sure why it would be otherwise. I normally use
ZSH as my shell, but I fail to see the significance in this case. It being
a bash script or not, ABS should require BASH (or whatever shell it needs)
to be installed and run it as needed. Both BASH and ZSH normally source
their environment on load, thus I still would expect this file to be read
on every 'makepkg' call, because that command forks and creates a new child
process with its own envir. Correct me if I am wrong.

Regards,
Konstantin

On Fri, Mar 24, 2017 at 1:41 AM, Uwe Koloska <kolewu at koloro.de> wrote:

> Am 23.03.2017 um 23:08 schrieb Konstantin Gizdov:
> > I am aware of the '/etc/makepkg.conf'. I read the Wiki. That's not what I
> > am talking about. A make command in a PKGBUILD build() did not accept my
> > tweaked $MAKEFLAGS. I had to explicitly give 'make $MAKEFLAGS' to get my
> > options to work. So I added it to the PKGBUILD of my packages. Maybe it
> > works now without it, but it didn't.
>
> Just a guess: How did you try to define the flag?  If it doesn't exist
> (and has been exported before) you have to export it for make to pick it
> up from the environment.  Setting the variable only makes it available
> in the current script (and a PKGBUILD is just a bash script setting
> well-known variables and using some predefined functions).
>
> Regards,
> Uwe
>