From owner-freebsd-questions@FreeBSD.ORG Sat Jan 16 23:55:23 2010 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D438106566B for ; Sat, 16 Jan 2010 23:55:23 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from worf.ds9.tecnik93.com (worf.ds9.tecnik93.com [81.196.207.130]) by mx1.freebsd.org (Postfix) with ESMTP id 22BEC8FC12 for ; Sat, 16 Jan 2010 23:55:22 +0000 (UTC) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by worf.ds9.tecnik93.com (Postfix) with ESMTPSA id 7164D22C5089; Sun, 17 Jan 2010 01:37:35 +0200 (EET) Date: Sun, 17 Jan 2010 01:37:22 +0200 From: Ion-Mihai Tetcu To: pav@FreeBSD.org Message-ID: <20100117013722.1893895c@it.buh.tecnik93.com> In-Reply-To: <1263673588.1541.60.camel@hood.oook.cz> References: <4B520C71.9080301@FreeBSD.org> <1263673588.1541.60.camel@hood.oook.cz> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.18.5; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/RlO=6AwUMR2Vt5bhdtazGSj"; protocol="application/pgp-signature" Cc: glarkin@FreeBSD.org, portmgr@FreeBSD.org, "b. f." , freebsd-questions@FreeBSD.org Subject: Re: Dislike the way port conflicts are handled now X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2010 23:55:23 -0000 --Sig_/RlO=6AwUMR2Vt5bhdtazGSj Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, 16 Jan 2010 21:26:28 +0100 Pav Lucistnik wrote: > Greg Larkin p=C3=AD=C5=A1e v so 16. 01. 2010 v 13:58 -0500: >=20 > > That's exactly what I proposed. The bsd.port.mk could be patched to > > support a new variable ("EARLY_CONFLICT_CHECK=3Dyes" or somesuch) that > > shifts the check-conflict target from its old position (part of the > > install sequence) to its new position (fetch?). > >=20 > > The default behavior (no mods to /etc/make.conf) would revert to > > the old conflict checking method. This may be something for > > portmgr@ to chime in on, and I'm cc'ing them now. There could be > > other reasons for this change that I'm unaware of. >=20 > What is the particular scenario that the new conflicts handling broke > for you? Often you really want to ignore locally installed packages > and then it's better to override LOCALBASE to /nonex or something > similar, instead of disabling conflict handling... I'd be very happy if I could: - fetch the distfiles, even if I have a conflicting port installed - be able to use portmaster -o to switch from one port to an other one that conflicts with it. - be able to at least compile a port (eg. for testing) without having to de-install the current one. I'm all in favor of restoring the old behavior with a switch available to turn on the new one. --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B --Sig_/RlO=6AwUMR2Vt5bhdtazGSj Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAktSTb4ACgkQJ7GIuiH/oeXTwQCgsPFZP7TIuNVY8V2dOCHJa70l 2HQAoKsCi8hS7JutGTl5qdQYv28ekjqb =FNi8 -----END PGP SIGNATURE----- --Sig_/RlO=6AwUMR2Vt5bhdtazGSj--