Okay, maybe I'm being a bit stupid here, but if I had I compiled wireshark several months ago, and it required libpcap, however the port for wireshark was upgraded BEFORE the port for libpcap... So, if I don't rebuild wireshark AFTER the libpcap upgrade I would have a problem like "The wireshark package depends on the major version of libpcap, and as such requires rebuild when a new major version of that package is pushed. <https://trac.macports.org/ticket/17361>"
But if I use port_upgrade, then I don't in fact jmr in this ticket even agreed that "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. " So, now there is an option for those of us wanting tools to work reliably, and don't wish to spend hours trying to determine which library version of hat dependancy was outdated by what to cause a bug, when a simple re-compile solves the issue the first time around. I fail to see the issue. Scott Bryan Blackburn wrote: > On Sat, May 09, 2009 at 04:28:46PM -0700, Scott C. Kennedy said: > >> Plus, when a dependency for a package changed significantly, then the >> program would terminate or act unexpectedly. For me, a longer compile >> time when updating packages to ensure that all my packages are linked to >> the most recent version of all of their dependencies is a good >> investment of time. >> > > 'port upgrade' when new dependencies are added should simply install those > ports, what is the problem you've seen, is there a ticket? > > Bryan > > >
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
