#41600: bison: update to 3.0.2 ------------------------------+---------------------- Reporter: akim.demaille@… | Owner: larryv@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: bison | ------------------------------+---------------------- Comment (by akim.demaille@…): Replying to [comment:27 rjvbertin@…]:

Who is *you* here?

Currently the portfile indicates that it doesn't install libraries, and that appears to be true. I don't think it's a particularly good idea to split up the package in this case.

Actually POSIX requires that we provide a `liby`. It's stupid and useless, but that just POSIX conformance. And since I would rather recommend installing `yacc`, I would also recommend installing `liby`. *However*, you can rest assured that no serious project would ever use this `liby`, it's really only meant for beginner experimenting their first parser. So do not bother making a separate package for `liby`, it really makes no sense. The case of the internationalization of the error messages is more relevant, however.

I'd be in favour of merging the +yacc variant into the main port, and also wondered about the examples. In fact, I'd be in favour of moving the examples to a variant; most people are probably not interested in them anyway because they install bison only as a result of some automatic dependency. (And most who do use the application won't need examples anymore.)

I disagree here. Bison is rarely a dependency since most packages ship their generated parser and don't need Bison at all from the end user point of view. So installing Bison is rather to use Bison yourself. In which case the documentation (and the examples do belong to the documentation) makes perfect sense. -- Ticket URL: <https://trac.macports.org/ticket/41600#comment:31> MacPorts <https://www.macports.org/> Ports system for OS X