Date: Fri, 28 Oct 2005 05:09:52 -0400 From: Gerard Seibert <gerard@seibercom.net> To: freebsd-questions@freebsd.org Subject: Re[2]: portupgrade stale dependencies Message-ID: <20051028050719.D60E.GERARD@seibercom.net> In-Reply-To: <cb5206420510280025h10f96272v4fb381c76aa83d6@mail.gmail.com> References: <200510271904.17908.ringworm01@gmail.com> <cb5206420510280025h10f96272v4fb381c76aa83d6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, October 28, 2005 3:25:14 AM, "Andrew P." <infofarmer@gmail.com= > Subject: Re: portupgrade stale dependencies Wrote these words of wisdom: > On 10/28/05, Michael C. Shultz <ringworm01@gmail.com> wrote: > > On Thursday 27 October 2005 18:49, Eric F Crist wrote: > > > On Oct 27, 2005, at 8:32 PM, John DeStefano wrote: > > > > On 10/27/05, Andrew P. <infofarmer@gmail.com> wrote: > > > >> On 10/27/05, John DeStefano <john.destefano@gmail.com> wrote: > > > >>> After clearing out the ports, updating ports (with portsnap) an= d > > > >>> source, and rebuilding the system and kernel... it seemed the > > > >>> ultimate > > > >>> problem was actually a dependency of the package to apache1.3. > > > >>> After I > > > >>> ran 'pkgdb -F' and "fixed" this dependency to point to apache2.= 1, > > > >>> but > > > >>> I still had trouble installing ports. > > > > > > At this point, what usually works for me is to: > > > > > > #cd /usr && rm -rf ./ports > > > > > > #mkdir ./ports && cvsup /root/ports-supfile > > > > > > The above will delete your ENTIRE ports tree, provided it's kept in= / > > > usr/ports and as long as you use cvsup (and your ports supfile is / > > > root/ports-supfile as mine is). When a whole bunch of ports stop > > > working, I find this is the easiest thing to do. > > > > > > The other thing I do is run a cron job every week that updates, via > > > cvsup, the ports tree. About once a year I perform the above, most= ly > > > to clean out the crap. Re-downloading your entire ports tree will = be > > > quicker if you don't use the ports-all tag and actually define whic= h > > > port segments you are interested in. For example, there's no real > > > reason to download all the x11/kde/gnome crap if you're doing this = on > > > a headless server that isn't going to serve X. > > > > > > HTH > > > > Replacing /usr/ports won't fix his problems, they reside in /var/db/p= kg. > > I may be a bit biased but I reaaly think John D. should try running > > portmanager -u (ports/sysutils/portmanager). Stale dependencies is a= non > > issue for portmanager. > > > > -Mike > > > I don't think that stale dependencies are an issue for > portupgrade as well, just add "-O" to the command- > line. ***** REPLY SEPARATOR ***** On 10/11/2005 5:29:42 PM, Gerard Replied: Personally, I feel that portmanager does a much better job of updating without the problems that seem to crop up so often using portupgrade. Just my 2=C2=A2. --=20 A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051028050719.D60E.GERARD>