Date: Sun, 8 Feb 2004 23:23:43 -0800 From: Kris Kennaway <kris@obsecurity.org> To: "W. Sierke" <ws+freebsd-questions@au.dyndns.ws> Cc: freebsd-questions@FreeBSD.org Subject: Re: How to deal with package conflicts (apache)? Message-ID: <20040209072343.GA3277@xor.obsecurity.org> In-Reply-To: <05dc01c3eed9$92527fe0$8464a8c0@ovirt.dyndns.ws> References: <05dc01c3eed9$92527fe0$8464a8c0@ovirt.dyndns.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
--k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 09, 2004 at 05:24:32PM +1030, W. Sierke wrote: > How should I deal with package conflicts such as > apache13/apache13-mod_ssl... >=20 > I've installed apache13-mod_ssl but a couple of other ports I want to > install want apache13 (specifically apache-1.3.29_1) which complains of a > package conflict (with apache+mod_ssl-1.3.29+2.8.16) so I'll have to force > the installation. Is there a way of convincing the new packages that > apache13-mod_ssl is an adequate substitute for apache13? Set the APACHE_PORT variable (to www/apachewhatever) in /etc/make.conf. This will only work with ports, not packages, for which one can only use the default settings. Kris --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAJzV/Wry0BWjoQKURAvWNAJwJCfOdiwerQuxul6JN7sr4lnbp/wCZAbYq k++xCb7HsZKF354eHmYlPqI= =cT95 -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209072343.GA3277>