#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 rjvbertin@…): Replying to [comment:40 akim.demaille@…]:
We're taking about an info file here, which is 537KB uncompressed, and 147KB when gzipped, and 112KB with bzip2, all of which are properly read by the info reader.
I know, which is why I didn't insist. But you'll agree with me that if one is to have a policy on this kind of question, you should start with applying it regardless of the size ;)
Why do we install man pages compressed, but no info files? And why keep all the ChangeLog etc. uncompressed too? (Heck, I'd rather see those 355KB of ChangeLog not be installed at all, and have the documentation! The priorities are really wrong here IMHO).
Good point on the info files (I'd add: who uses info files these days? The times I venture there they were strict but less readable copies of the manpages.) Note though that HFS+ can handle compression, and there is already a patch to portimage.tcl that causes the install (activation) of a port to be done using hfs compression. AFAIK that uses zip compression, which can already give appreciable gains. As to installing the ChangeLog et al.: that doesn't appear to be standard with MacPorts. I was under the impression that you added them to comply with FOSS guidelines and how things are done on Linux. Maybe the official port maintainer had the same impression, maybe it's he who decided to do this.
Yet, I am really surprised by your figures (the number of packages that do depend on Bison explicitly to build), so my point is moot.
If I'd had to guess, I'd say that this may be due to the fact that a considerable number of FOSS packages have to invoke autogen etc. before they can be built. That may make it necessary to parse the bison/yacc source files, or maybe they just have to be regenerated for OS X for other reasons. The only project where I've had to deal with bison explicitly, xxdiff, ships only the yacc sources and than invokes bison through qmake or through the qmake generated Makefile. (Reminds me I should check if it is still incompatible with bison 3 ...)
I can live with the documentation not being installed by default (in which case it should be the same for the examples: they also belong to +doc).
I'll leave this up to the official port maintainer to decide, as with the ChangeLog etc. thing. -- Ticket URL: <https://trac.macports.org/ticket/41600#comment:41> MacPorts <https://www.macports.org/> Ports system for OS X