Date: Sun, 13 Feb 2005 20:37:47 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: "Michael C. Shultz" <reso3w83@verizon.net>, freebsd-questions@freebsd.org Subject: Re: Updated perl - broke stuff Message-ID: <2147483647.1108327067@[192.168.2.100]> In-Reply-To: <200502131815.21142.reso3w83@verizon.net> References: <200501271852.j0RIqQ9t010411@mp.cs.niu.edu> <200502131642.59595.ean@hedron.org> <04e901c51217$c3d5e590$7702a8c0@officeeagle> <200502131815.21142.reso3w83@verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Sunday, February 13, 2005 6:15 PM -0800 "Michael C. Shultz" <reso3w83@verizon.net> wrote: > > Pkgdb -F is what screws up the installed ports registry. Here is an > example of what happens: > > 1. port-A needs dependency port-B installed > 2. port-B is installed > 3. port-A is installed and marks its registry as being dependent on > port-B > > and here is where things go wrong using sysutils/portupgrade: > > 4. port-B gets upgraded to port-B.1 and portupgrade reports port-A > has a stale dependency. > > Then you run pkgdb -F and port-A's registry is changed to say it was > built with port-B.1, portupgrade claims this "fixes" the registry when > it really breaks it. > > Remember, port-A was built with port-B, not port-B.1 and the correct way > to "fix" the stale dependency is to upgrade port-A so it is built with > the newer dependency. > > sysutils/portmanager also updates ports, put it doesn't cheat. When > port-B became port-B.1 portmanager will rebuild port-A using port-B.1 > as the dependency. port-A's registry stays reliable, reflecting how the > port was really build instead of how we wished it were built. > Thanks, Mike. I believe I start reading the man page for portmanager. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2147483647.1108327067>