handling IGNORE messages for DUD builds

[Bernhard Froehlich]

On 25.02.2012 23:25, Bernhard Froehlich wrote:
> On 25.02.2012 20:31, Joe Marcus Clarke wrote:
>> On 2/25/12 1:58 PM, Bernhard Froehlich wrote:
>>> On 25.02.2012 19:03, Joe Marcus Clarke wrote:
>>>> On 2/25/12 12:15 PM, Bernhard Froehlich wrote:
>>>>> Has anyone an idea how to get IGNORE/FORBIDDEN/NO_PACKAGE 
>>>>> messages for
>>>>> port builds that went dud? Currently there is no easy way to find 
>>>>> out
>>>>> why a port went dud.
>>>>
>>>> The dud state is a reported state.  You could use an SQL query:
>>>>
>>>> SELECT * from build_ports WHERE last_status = 'DUD';
>>>
>>> I am asking for the exact IGNORE reason as in make -V IGNORE. 
>>> Reporting
>>> that in an build logfile would also be fine.
>>>
>>> I've tried to get that info via make -V IGNORE in a postPortBuild 
>>> hook
>>> but I always get 'duds' and I'm not sure why.
>>>
>>
>> How is your hook written?  What about:
>>
>> cd ${chroot}/usr/ports/${PORTDIR}
>> make -V IGNORE
>
> It seems to work fine in the hook with:
>
> cd ${PB}/${BUILD}/a/ports/${PORTDIR} && make -V IGNORE
>
> Thanks for the help!

I've thought a bit more about it and don't think it's correct because 
it doesn't do this in the chroot. So options and the jail environment 
are not respected.

-- 
Bernhard Froehlich
http://www.bluelife.at/