#17361: wireshark-1.0.4 needs rebuild after upgrading libpcap --------------------------------+------------------------------------------- Reporter: brad@… | Owner: opendarwin.org@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: wireshark --------------------------------+------------------------------------------- Changes (by mr_bond@…): * owner: macports-tickets@… => opendarwin.org@… -- Ticket URL: <http://trac.macports.org/ticket/17361#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#17361: wireshark-1.0.4 needs rebuild after upgrading libpcap ---------------------------------+------------------------------------------ Reporter: brad@… | Owner: ricci@… Type: defect | Status: closed Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: invalid | Keywords: Port: wireshark | ---------------------------------+------------------------------------------ Changes (by ricci@…): * status: assigned => closed * resolution: => invalid Comment: Given that wireshark already depends on libpcap, how did you install the new libpcap without re-installing wireshark? In particular, if you did a force uninstall/install of libpcap without uninstalling wireshark, then there's no surprise that it broke. If this is not what happened, please re-open and report the exact steps taken the produce this problem. -- Ticket URL: <http://trac.macports.org/ticket/17361#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#17361: wireshark-1.0.4 needs rebuild after upgrading libpcap ---------------------------------+------------------------------------------ Reporter: brad@… | Owner: ricci@… Type: defect | Status: reopened Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: Port: wireshark | ---------------------------------+------------------------------------------ Comment(by ricci@…): Replying to [comment:5 jmr@…]:

Wireshark was last updated 5 weeks ago, and libpcap was last updated one week ago. It's quite easy to imagine a user installing wireshark (and the old libpcap as a dep), and then running `port upgrade outdated` a while later, thus ending up with a new libpcap that the installed wireshark doesn't work with.

Bumping wireshark's revision should take care of this.

"port upgrade" should rebuild dependencies, and in the guide this appears to be the case (though it isn't entirely clear): "The upgrade option upgrades installed ports and their dependencies when a Portfile in the repository has been updated after a port was installed." If someone uses "port upgrade outdated" and the bumped libpcap doesn't result in dependencies (like wireshark) being rebuilt, I think that's a bug with "port upgrade" and should not be fixed by band-aiding ports every time their dependencies are changed. If the filer of the ticket could include the commands (and other details) that were used to get their install into this state, that would be helpful. -- Ticket URL: <http://trac.macports.org/ticket/17361#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#17361: wireshark-1.0.4 needs rebuild after upgrading libpcap ---------------------------------+------------------------------------------ Reporter: brad@… | Owner: ricci@… Type: defect | Status: reopened Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: Port: wireshark | ---------------------------------+------------------------------------------ Comment(by ricci@…): I also don't feel that the right solution is to give wireshark a revision bump to handle a dependency upgrade. Is there a reason we don't make make 'port upgrade -R' the default? -- Ticket URL: <http://trac.macports.org/ticket/17361#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#17361: wireshark-1.0.4 needs rebuild after upgrading libpcap ---------------------------------+------------------------------------------ Reporter: brad@… | Owner: ricci@… Type: defect | Status: reopened Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: Port: wireshark | ---------------------------------+------------------------------------------ Comment(by ricci@…): Replying to [comment:9 blb@…]:

Replying to [comment:8 ricci@…]:

...

I also don't feel that the right solution is to give wireshark a revision bump to handle a dependency upgrade. Is there a reason we don't make make 'port upgrade -R' the default?

A minor update to base-level ports (eg, zlib, libpng, etc) would then trigger a rebuild of many, many ports.

Yes, it would. When that's the "right" thing to do (and when it is not) is not obvious from what knowledge we can (currently) provide in a Portfile, nor is it across-the-board easy to tell when a minor rev of a library will have API changes (it does happen, most unfortunately). It would make a great project for somebody to work on (next summer?) - to have port grok when it should do dependent rebuilds and when it should not. Given the pain of rebuilding so many things, having 'port upgrade -R' be the default is probably not the right answer. Having some sort of key in the Portfile that indicates that the port author believes the change does require dependent rebuilds would (appear to) solve the problem. -- Ticket URL: <http://trac.macports.org/ticket/17361#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS