Date: Tue, 28 Nov 2006 10:01:05 -0500 From: Vivek Khera <vivek@khera.org> To: ports@freebsd.org Subject: stale dependencies and portupgrade Message-ID: <5D017181-7215-4CB6-A459-4A40751AB39A@khera.org>
next in thread | raw e-mail | index | archive | help
--Apple-Mail-6--412211960 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I've been using portupgrade for a long time now. Recently I've been noticing (though I'm sure it has been happening all along) that dependencies are not cleanly propagated to other ports. Example: p5-Expect used to depend on p5-IO-Stty which was removed from ports recently. rt36 depends on p5-Expect, so got a transitive dependency to this dead port. Upgrading p5-Expect using "portupgrade -Rr" took care of the direct dependency, but the upstream ports still had the registered dependency to p5-IO-Stty. I had to force- uninstall that port then run "pkgdb -F" to remove that dependency. Similarly, with a portupgrade of portupgrade itself, most of my machines lost the dependency to ruby18-bdb1 package. The only way out of that was to do a delete of portupgrade and run a fresh make install in the port directory. I suppose the bug is that I expected portupgrade -Rr to recompute the dependency lists of the upstream ports to take into account any changing dependencies of the updated port. Do other port manager utilities take this type of change into account? At this point, I'm not sure any of my dependencies are accurate on the complex ports like RT. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. MailerMailer, LLC Rockville, MD http://www.MailerMailer.com/ +1-301-869-4449 x806 --Apple-Mail-6--412211960--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D017181-7215-4CB6-A459-4A40751AB39A>