Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Oct 2005 11:25:14 +0400
From:      "Andrew P." <infofarmer@gmail.com>
To:        "Michael C. Shultz" <ringworm01@gmail.com>
Cc:        Eric F Crist <ecrist@secure-computing.net>, freebsd-questions@freebsd.org, John DeStefano <john.destefano@gmail.com>
Subject:   Re: portupgrade stale dependencies
Message-ID:  <cb5206420510280025h10f96272v4fb381c76aa83d6@mail.gmail.com>
In-Reply-To: <200510271904.17908.ringworm01@gmail.com>
References:  <f2160e0d0510151746n28cdbb25s2150337c0c6f7cfc@mail.gmail.com> <f2160e0d0510271832s68dc34c3ge7c7a04e1d20bf60@mail.gmail.com> <0E2AAC01-B12D-4A7A-A986-B7A57DDDEDFF@secure-computing.net> <200510271904.17908.ringworm01@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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) and
> > >>> 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, mostly
> > 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 which
> > 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/pkg.
> 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
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o=
rg"
>

I don't think that stale dependencies are an issue for
portupgrade as well, just add "-O" to the command-
line.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420510280025h10f96272v4fb381c76aa83d6>