On Fri, Jan 21, 2011 at 06:45:20PM -0500, Daniel J. Luke wrote: > On Jan 21, 2011, at 6:43 PM, Jack Howarth wrote: > > > >> So then one of thee things happened: > >> > >> - There is some bug in port where pymol was rebuilt before libpng > >> - pymol didn't have a dependency on libpng listed (which would be a bug in > >> the pymol port) > >> - pymol wasn't rev-bumped (or was rev-bumped after your selfupdate > >> happened, and you unfortunately got the libpng bump but not the pymol bump) > > > > http://trac.macports.org/changeset/75159 > > > > says it isn't either of the last two possibilities. Without even simple > > logging of port's > > activity ala yum.log, it is impossible to rule out the first possibility > > one way or the other. > > you update from the subversion repo?
I have a standard install with appears to use rsync. According to http://www.macports.org/install.php#svn the svn option is oriented towards developers. So what you are telling me is that the dependency mechanism of port is fragile for the typical MacPorts user. Jack > > Do you know if the rsync repo does an atomic update of all the portfiles (ie, > you know that you are gaurenteed to not have had an updated libpng port but > not an update pymol port?) > > logging isn't the only way to debug problems. > -- > Daniel J. Luke > > +========================================================+ > > | *---------------- [email protected] ----------------* | > > | *-------------- http://www.geeklair.net -------------* | > > +========================================================+ > > | Opinions expressed are mine and do not necessarily | > > | reflect the opinions of my employer. | > > +========================================================+ > > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
