On Wed, Nov 05, 2008 at 02:19:15AM -0500, Aaron W. Hsu wrote: > Jasper, > > Thanks for your reply... > > > And my attempt to remove that old library: > > with what commad are you removing that old library? obviously > not pkg_delete. that would solve the problem actually... > > I was just attempting to rm the main one. Reading through the the > pkg_delete man page, I cannot find a way to delete the glib2 package > without also deleting all of its dependencies. If you know some > way to do this, I am all ears.
Get real.. ports depending on glib2 are built _against_ this glib2. If you remove the old version and install a new one (with a major bump), you really think these ports will get along with that ? The solution is to delete glib2, note the depending ports, and rebuild them against the new glib2. Or wait for a snapshot. > Nonetheless, shouldn't a ports update go through smoothly without > breaking? This seems like a problem with the port assuming a clean > system. No. For some big ports like that, it's generally impossible. using pkg_add -r will keep the old libraries around for dependencies in .libs-glib2-xxxx, and they will still be picked up by the build. And anyway, the 'supported' update is pkg_add -ui. Landry
