tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Sanitising make environment in pkgsrc



Joerg Sonnenberger <joerg%britannica.bec.de@localhost> writes:

> On Tue, Aug 16, 2011 at 04:36:08PM -0500, Tim Zingelman wrote:
>> In that thread I pointed out that a common solaris boostrap passes
>> variables in the environment...
>> 
>>     env CC=/opt/studio12/SUNWspro/bin/cc \
>>           SUNWSPROBASE=/opt/studio12/SUNWspro \
>>           ./bootstrap --abi=64
>> 
>> does this patch still allow that (I had hoped to answer that question
>> myself by testing, but ENOTIME today.)
>
> Usage like this is exactly my concern with the wildcard scrub.
> It's not specific to SunPRO either -- there are a number of other
> environmental variables people might want to use sanely to affect the
> build.

I see your point, but on the other hand one of the core doctrines of
pkgsrc is repeatable builds.  While this is primarily about not having
installed packages be picked up as implicit dependencies, I can see the
point of not having random environment variables in the user's
environment affect things either.

Perhaps a solution is to place environment variables in mk.conf, and
thus control the environment?

Attachment: pgporAVdmhGnj.pgp
Description: PGP signature



Home | Main Index | Thread Index | Old Index