Date: Thu, 25 Sep 2003 19:13:58 -0700 From: Kris Kennaway <kris@obsecurity.org> To: K Anderson <freebsduser@comcast.net> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Ports woes. Message-ID: <20030926021358.GA67939@rot13.obsecurity.org> In-Reply-To: <3F7374D7.9050604@comcast.net> References: <00df01c38185$2255aee0$5864a8c0@patience> <20030923050226.GC50083@rot13.obsecurity.org> <3F7374D7.9050604@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 25, 2003 at 04:05:59PM -0700, K Anderson wrote: > Does this possibly clear up things? Yeah, that's all expected behaviour.. 1) when upgrading ports you have to upgrade ports in the correct order, i.e. if X depends on Y then you have to update Y before you update X. sysinstall doesn't do this, ports will at least notice that you have tried to install a new version of Y on top of an old version or have tried to update X when you should have first updated Y. The easiest way to update ports in the correct order is to use the portupgrade port. 2) packages depend explicitly on other packages, in particular if you have apache-X installed and it's looking for apache-Y then it will try to install it, and won't be satisfied by the apache-X installation. Kris --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/c6DlWry0BWjoQKURAv9zAJ4itRO8grb8W5pCw8CzQ7UWoA/hTwCgkOGy H3T+v6LGVy7B88lq4C1wUNg= =seNN -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030926021358.GA67939>