ports/59254: ports that write something after bsd.port.mk

[Oliver Eikemeier]

Sergei Kolobov wrote:

> It's my PR, and I didn't have a chance to follow-up on it for some time.
> I am now working on a better patch.
> 
> On 2003-11-14 at 02:27 +0100, Oliver Eikemeier wrote:
> 
>>David O'Brien wrote:
>>
>>>Maybe we need a knob (USE_NEW_CONFIGURE_TUPLE) or something so that
>>>there is complete consistency in the GNU tuple string.
>>
>>OR make it dependend on GNU_CONFIGURE/HAS_CONFIGURE or use
>>GNU_CONFIGURE=	new
>>but we should discuss this as a followup of PR 52917
> 
> I think it's quite safe to default to the new CONFIGURE_TARGET value,
> and use
> 
> GNU_CONFIGURE=	old	(or, perhaps, 2.13)
> 
> only for those ports that breaks.
> 
> I will submit the updated patch shortly.

How about doing something like
cd ${CONFIGURE_WRKSRC} && ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} --version | sed -ne 's/.*autoconf version \([0-9.]*\).*/\1/p'