[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: pkg/48157: pkgsrc 2013Q2 make-system exeeds max. command line length
Hi to all,
I don't think that placing variables only needed for "some" builds - for
whatever reasons - in /etc/mk.conf is a real good sollution.
This special variable is used to suppress lots of messages while
building some packages during "initial" system installation - the state
of the network is unknown at this time.
(We've automated the system setup a little bit, because it is not
practical to setup (or upgrade) many systems by hand in a consistant way.)
The variable should not be setup for builds later if the system is
completely configured and running.
And I also don't think that editing in /etc/mk.conf "all the time" is a
good idea either.
/etc/mk.conf is the right place to setup system depedant things - e.g.
support for the different compilers on a Solaris system - or
"security"-setups like to disallow automatich installation into /etc/shells.
But neverless, it is no good idea to replicate command line options
while calling make in a recursive way. And this is done!
You will loose even without setting some additional things on the
command line if the recursion is deep enought.
So I don't think to solve this issue is "to hack around for a special
usage" as mentioned in an other reply before.
And I also don't thing that specifying variables with "-D .." is an
unexpected usage. E.g. the messages when additional licenses are needed
to be accepted suggest to do this.
mary christmas and a happy new year
Thomas Klausner wrote:
The following reply was made to PR pkg/48157; it has been noted by GNATS.
From: Thomas Klausner <wiz%NetBSD.org@localhost>
To: NetBSD bugtracking <gnats-bugs%NetBSD.org@localhost>
Subject: Re: pkg/48157: pkgsrc 2013Q2 make-system exeeds max. command line
Date: Fri, 13 Dec 2013 19:21:05 +0100
On Fri, Dec 13, 2013 at 01:15:00PM +0000, Wolfgang Stukenbrock wrote:
> The "-D ALLOW_VULNERABLE_PACKAGES" (and some other options) are placed
> on the command line for each recursive package build again and again and
> again. So triggering the problem needs a deep recursion tree.
That doesn't sound like a good idea.
How about putting it in your /etc/mk.conf like the other variables you set?
Main Index |
Thread Index |