Opened 11 years ago
Closed 10 years ago
#39910 closed request (wontfix)
Request for bison2 port due to backwards-incompatible changes in Bison 3.0
| Reported by: | cooljeanius (Eric Gallager) | Owned by: | mww@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | hubsif, jeremyhu (Jeremy Huddleston Sequoia), ryandesign (Ryan Carsten Schmidt), mww@…, dcecchin@…, nonstop.server@…, akimd (Akim Demaille), bgschaid@… | |
| Port: | bison2 |
Description
The changelog for bison 3 lists some incompatibilities with older versions: http://savannah.gnu.org/forum/forum.php?forum_id=7663
While the bison port was at version 2, there was a separate port for the previous version of bison, which was bison1 at the time. Now there's still the bison1 port, but it skips over version 2 straight to version 3. I'd like a separate bison2 port to fill this gap.
(This was split off from comment:ticket:39909:4 btw)
Attachments (6)
Change History (27)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
| Port: | bison1 bison removed |
|---|---|
| Summary: | bison: Now that the port is for version 3, add a new port for bison2 → Request for bison2 port due to backwards-incompatible changes in Bison 3.0 |
| Version: | 2.2.0 |
comment:2 Changed 11 years ago by cooljeanius (Eric Gallager)
More ports suffering from incompatibilites:
comment:ticket:39598:109 (good grief that's a lot of comments on that ticket...)
#39924 (actually an issue with building bison itself, but having a bison2 to fall back on in the meantime could be useful)
comment:4 follow-up: 10 Changed 11 years ago by dbevans (David B. Evans)
| Cc: | mww@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to mww@… |
Either reverting the current bison port to 2.7.1 or creating a separate port of that version would work for me (as a webkit-gtk maintainer) but if bison (3.0) and bison2 would conflict then I think the utility would be questionable.
Bison1 is seriously outdated and has no current dependents so should probably be removed.
A quick check of bison dependents shows 93 at this moment. I'm sure that more than one uses the deprecated features that are now removed in bison 3.0 (#39923) although I haven't tested them all. And there is no evidence that any port actually requires bison 3.0 at this point.
So my vote overall would be to revert bison to the previous 2.7.1 version until the impact of upgrading to 3.0 is evaluated with respect to its current dependents. Of course, I would defer to the bison maintainer as to his preferred resolution but encourage this to be handled as soon as possible since the breakage in webkit-gtk blocks a number of other ports. To start, these include gimp2, epiphany, yelp, devhelp and the many other GNOME ports that depend on yelp.
comment:5 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Owner: | changed from mww@… to jeremyhu@… |
|---|
If nobody comments on this in the next 12 hours, I'm going to revert bison at some point tomorrow.
comment:7 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Cc: | ryandesign@… added |
|---|
comment:8 Changed 11 years ago by jmroot (Joshua Root)
| Cc: | mww@… added |
|---|
comment:10 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to devans@…:
if bison (3.0) and bison2 would conflict then I think the utility would be questionable.
bison1 currently doesn't conflict with bison, if it's able to do that, then I don't see why bison2 and bison3 would have to conflict... Instead, I would expect them to be able to be installed in parallel, as well.
Edit: in my local ports tree all 3 versions of bison install in parallel with no problem whatsoever, so my expectations turned out to be correct (at least for me).
comment:12 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Owner: | changed from jeremyhu@… to mww@… |
|---|
comment:14 follow-up: 15 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to jeremyhu@…:
Akim Demaille opened ticket #41600 to add back bison3, which presumably would revert that... (I'm still hoping that MacPorts would be able to have both versions at the same time...)
comment:15 follow-up: 16 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to egall@…:
I'm still hoping that MacPorts would be able to have both versions at the same time...
You're welcome to contribute a Portfile if you'd like to see this happen.
comment:16 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to larryv@…:
Replying to egall@…:
I'm still hoping that MacPorts would be able to have both versions at the same time...
You're welcome to contribute a Portfile if you'd like to see this happen.
OK, just a sec, I have to strip out some things I added for my local copies that might not be suitable for trunk...
Changed 11 years ago by cooljeanius (Eric Gallager)
| Attachment: | Portfile-bison1.diff added |
|---|
diff between my bison1 portfile and the one that existed previously
Changed 11 years ago by cooljeanius (Eric Gallager)
| Attachment: | Portfile.2 added |
|---|
Portfile for bison2
Changed 11 years ago by cooljeanius (Eric Gallager)
| Attachment: | Portfile-bison2.diff added |
|---|
diff between my bison2 portfile and previous bison2 portfile
Changed 11 years ago by cooljeanius (Eric Gallager)
| Attachment: | Portfile.3 added |
|---|
Portfile for bison3
Changed 11 years ago by cooljeanius (Eric Gallager)
| Attachment: | Portfile-bison3.diff added |
|---|
diff between my bison3 portfile and the portfile for bison the last time it had been at bison3
comment:17 Changed 11 years ago by cooljeanius (Eric Gallager)
OK, I added portfiles for 3 different versions of bison that install in parallel. We'll probably want to add unversioned symlinks to the executables for the port of the version that we want to support.
comment:20 follow-up: 21 Changed 10 years ago by akimd (Akim Demaille)
Can we move forward? It looks like all the work is done, but not installed.
comment:21 Changed 10 years ago by larryv (Lawrence Velázquez)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I’ll be handling the 3.0.4 update in #41600 but will not be adding a port for Bison 2 because I don’t like versioned ports, and most ports build fine with Bison 3.
The backwards-incompatible changes are actually listed in the NEWS file.