C. Florian Ebeling wrote: > This is a message from the couchdb list also involving MacPorts. > > ---------- Forwarded message ---------- > From: Ivan Avery Frey <[email protected]> > Date: Sun, Dec 14, 2008 at 7:05 PM > Subject: MacPorts Bug? > To: [email protected] > > I just got couchdb working again on my PowerBook G4 with Tiger (10.4.11). > > What happened was after I installed couchdb I did a "sudo port -d > upgrade couchdb". The icu port got upgraded to 4.0. Now when I went to > run couchdb it went looking for 3.8 versions of the ICU libraries which > no longer existed. > > A uninstall install of couchdb fixed the problem. Have I reported this > bug in the right place? > --- snip --- > > Do we have any slick response for this, or does 'port upgrade' just keep > the dependants binaries with dangling links to nothing. > > I would have thought that the nice answer would be that the dependant should > actuallt point to the depot location of the library, which should be > in the same > location after the upgrde as before. Only I'm not sure that e.g. a > autotool package > as couchdb looks into depot, and not just in /opt/local/lib. > > Does a simple 'port upgrade' can leave broken packages behind? Is there maybe > an > open ticket for this?
Yes, it's a real problem when library versions change. Ticket: <http://trac.macports.org/ticket/17473> - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
