From owner-freebsd-ports@FreeBSD.ORG Wed Jun 13 18:00:42 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8C6016A469 for ; Wed, 13 Jun 2007 18:00:42 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 2697913C458 for ; Wed, 13 Jun 2007 18:00:41 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Jun 2007 18:00:39 -0000 Received: from nat-wh-1.rz.uni-karlsruhe.de (EHLO mobileKamikaze.norad) [129.13.72.169] by mail.gmx.net (mp001) with SMTP; 13 Jun 2007 20:00:39 +0200 X-Authenticated: #5465401 X-Provags-ID: V01U2FsdGVkX19TlbRYkshTKaHkLguGa8BEAozWHVHZa+yqo0Yu1b gDdjVyENop5PaR Message-ID: <467030C0.9020508@gmx.de> Date: Wed, 13 Jun 2007 20:00:32 +0200 From: "[LoN]Kamikaze" User-Agent: Thunderbird 2.0.0.0 (X11/20070603) MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <466279CC.8030200@gmx.de> <4663D0B9.4000602@FreeBSD.org> <46701E0B.6010804@gmx.de> <46701FAD.7020204@FreeBSD.org> <20070613173159.GK90672@droso.net> In-Reply-To: <20070613173159.GK90672@droso.net> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: make update broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2007 18:00:43 -0000 Erwin Lansing wrote: > On Wed, Jun 13, 2007 at 06:47:41PM +0200, Alex Dupre wrote: >> [LoN]Kamikaze wrote: >>> It still seems not to be fixed and I cannot find the PR either. Can you give me >>> the number? >> I didn't open a PR, I contacted directly who proposed/committed that >> change and portmgr. But after a couple of mail exchanges nobody took a >> final decision (i.e. I'm still waiting a reply or an action). >> > As I described earlier, SUP_UPDATE, CVS_UPDATE and PORTSNAP_UPDATE are > mutually exclusive and cannot be used at the same time. That it worked > before was an artifact which has been fixed. That is doesn't work > anymore means the designed behaviour finally has been fixed and not > broken :-) So you cannot maintain /usr/src if you wish to use portsnap for /usr/ports? The intended behaviour is stupid. I would prefer a fall back to portsnap if PORTSSUPFILE is not provided.