Date: Thu, 29 Mar 2007 16:41:06 -0400 From: Gerard Seibert <gerard@seibercom.net> To: freebsd-questions@freebsd.org Subject: Re: the art of pkgdb -F Message-ID: <20070329164106.27389f8a@localhost> In-Reply-To: <20070329204005.1c3b7130@gumby.homeunix.com> References: <20070328011712.GR11147@tigger.digitaltorque.ca> <20070327202842.1678265c.freebsd@dfwlp.com> <d7195cff0703272219r3e504bd5tb09ca5acd3f82776@mail.gmail.com> <20070328212432.669353e4@gumby.homeunix.com> <20070329003659.GW11147@tigger.digitaltorque.ca> <20070329121553.070a6321@localhost> <20070329204005.1c3b7130@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_tO5Afm/85fnX0gF9oC3rxhU Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 29 Mar 2007 20:40:05 +0100 RW <fbsd06@mlists.homeunix.com> wrote: > Portmanager is really no better, the dependencies recorded in the > package database are also recursive. The big problem with gettext > was that a lot of port failed to build afterwards, leaving them with a > missing library. I have had problems in the past getting 'portupgrade' to properly update all of the dependencies required when doing a major update; i.e., 'gettext'.=20 On the other hand, I have never had a problem using 'portmanager' provided I used the '-p -f' flags. Portmanager can update its list of ports that need updating on the fly. I do not believe that either portupdate or portmaster have that ability. I noticed that when doing the 'gettext' update, it twice recalculated the number of ports that needed to have their dependencies updated. It would probably behoove anyone prior to doing a massive update to clean out the '/usr/ports/distfiles' directory and possibly running 'portsclean -C -D -l -PP' to insure that any old crud was not laying around. It certainly couldn't hurt. Just my 2 cents. --=20 Gerard Be careful how you get yourself involved with persons or situations that can't bear inspection. --Sig_tO5Afm/85fnX0gF9oC3rxhU Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGDCRiFCqdq4D1ybYRArOGAKC7XGZueCAHViA65jBf2+p5EmUlXwCgovI7 Fw+i4tPSutthgJc+xuWvPYQ= =fBr+ -----END PGP SIGNATURE----- --Sig_tO5Afm/85fnX0gF9oC3rxhU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070329164106.27389f8a>