yacc/bison

[Ryan Schmidt]

On Apr 8, 2009, at 02:33, Markus Weissmann wrote:

> On 8 Apr 2009, at 06:45, Ryan Schmidt wrote:
>
>> The +yacc variant was added to the bison port in r10216 when it  
>> was updated to version 2.0. No explanation why it was a variant  
>> instead of always on.
>
> If in doubt, I try to mimic the FreeBSD ports -- thats tried and  
> tested already for the "closest relative" OS. I recall there were  
> some ports that failed due to expecting "bison1" behind 'yacc'..

Ah, ok.


>> This sounds like a great example of where we should remove the  
>> variant and have bison always include yacc support.
>
> Thinking about enabling 'yacc' by default, there are (at least) 3  
> candidates to claim the 'yacc' executable: bison1, bison (version  
> 2), byaccj and bisoncpp [1];

Ok, didn't know those existed.

Perhaps bison's yacc could be its own port? Then one could declare a  
dependency on "path:bin/yacc:bison-yacc".


> Another solution would be to install the yacc/bison2 executable as  
> 'yacc2' or as 'yacc' in $prefix/lib/bison/bin -- thought?

If you go this route, ${prefix}/libexec/bison/ would be a better  
place than ${prefix}/lib/bison/bin/, based on my understanding of  
portheir(7), as used e.g. in the wine port.