[MacPorts] #17361: wireshark-1.0.4 needs rebuild after upgrading libpcap

[MacPorts]

#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