From owner-freebsd-ports@FreeBSD.ORG Mon Jun 18 10:51:21 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 C4C2E16A46B for ; Mon, 18 Jun 2007 10:51:21 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from andxor.it (relay.andxor.it [195.223.2.3]) by mx1.freebsd.org (Postfix) with SMTP id E4ABB13C469 for ; Mon, 18 Jun 2007 10:51:20 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: (qmail 2817 invoked from network); 18 Jun 2007 10:51:18 -0000 Received: from unknown (HELO ale.andxor.it) (192.168.2.5) by andxor.it with SMTP; 18 Jun 2007 10:51:18 -0000 Message-ID: <467663A6.3080006@FreeBSD.org> Date: Mon, 18 Jun 2007 12:51:18 +0200 From: Alex Dupre User-Agent: Thunderbird 2.0.0.4 (X11/20070617) 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> <46704964.7000205@FreeBSD.org> In-Reply-To: <46704964.7000205@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Mon, 18 Jun 2007 10:51:21 -0000 Alex Dupre ha scritto: > Erwin Lansing wrote: >> As I described earlier, SUP_UPDATE, CVS_UPDATE and PORTSNAP_UPDATE are >> mutually exclusive and cannot be used at the same time. From src/Makefile.inc1: # update # # Update the source tree, by running cvsup and/or running cvs to update # to the latest copy. From ports/Makefile rev. 1.61 commit log: Allow both SUP_UPDATE and CVS_UPDATE to be used, similar to src/Makefile The same commit introduced the check ".if defined(SUP_UPDATE) && !defined(PORTSSUPFILE)" with a different meaning from what you say. All the docs I found says explicitly (and does accordingly) that SUP_UPDATE and CVS_UPDATE are *not* mutually exclusive and that SUP_UPDATE can be defined *without* PORTSUPFILE. >> Please send-pr your patch, but >> please also add documentation of the new meaning of PORTSNAP_UPDATE. > > I'll do it. PR 113819 -- Alex Dupre