On 15 January 2016 at 14:01, arnaud gaboury <arnaud.gaboury(a)gmail.com> wrote:
On Fri, Jan 15, 2016 at 12:48 PM, arnaud gaboury
<arnaud.gaboury(a)gmail.com> wrote:
> On Fri, Jan 15, 2016 at 12:46 PM, Patrick O'Callaghan
> <pocallaghan(a)gmail.com> wrote:
>> On Fri, 2016-01-15 at 11:42 +0100, arnaud gaboury wrote:
>>> I need to unset one of my environment variable to successfully build
>>> a
>>> rpm package.
>>>
>>> I added this in my .spec file, but apparently it doesn't work:
>>>
>>> -------------------------------------------------------
>>> if [ -n $R_PROFILE_USER ];then
>>> unset R_PROFILE_USER
>>> fi
>>> ------------------------------------------------
>>>
>>> What is the correct way to unset for build time a env variable?
>>
>> Why do you need the test? Just unset it directly.
> ok. In case this variable does not exist, will the build stop?
> Anyway to save the variable value, unset and restore at %post ?
After more tests, best is indeed to modify a binary option using the
alias function. I can't find any entry on this. Adding
alias foo='foo --option' does not work.
Best plan for reproducible builds is to just use mock - then you get a
clean environment and don't have to worry about stuff like this,