Date: Sun, 17 Jan 2010 09:59:29 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: "b. f." <bf1783@googlemail.com>, glarkin@freebsd.org, pav@freebsd.org, portmgr@freebsd.org, Ion-Mihai Tetcu <itetcu@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: Dislike the way port conflicts are handled now Message-ID: <alpine.BSF.2.00.1001170949230.58984@wonkity.com> In-Reply-To: <4B52C94B.10809@infracaninophile.co.uk> References: <d873d5be1001161001i5d398205hea3d2ec1978ee3f@mail.gmail.com> <4B520C71.9080301@FreeBSD.org> <1263673588.1541.60.camel@hood.oook.cz> <20100117013722.1893895c@it.buh.tecnik93.com> <4B52C94B.10809@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 17 Jan 2010, Matthew Seaman wrote: > Ion-Mihai Tetcu wrote: > >> 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. > > +1 > > Although a big fat warning message at fetch or build phase when operating on > a port with conflicts wouldn't go amiss. Agreed. A warning would give time to interrupt a big distfile fetch or build without taking that option away by default, or encouraging disabling conflict checks altogether. -Warren Block * Rapid City, South Dakota USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1001170949230.58984>