From owner-freebsd-ports@FreeBSD.ORG Sat Jan 1 23:46:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF332106566C for ; Sat, 1 Jan 2011 23:46:15 +0000 (UTC) (envelope-from marco+freebsd-ports@lordsith.net) Received: from trinity.lordsith.net (trinity.lordsith.net [82.168.152.70]) by mx1.freebsd.org (Postfix) with ESMTP id 5B7038FC13 for ; Sat, 1 Jan 2011 23:46:15 +0000 (UTC) Received: by trinity.lordsith.net (Postfix, from userid 1001) id AE8146EA1; Sun, 2 Jan 2011 00:46:11 +0100 (CET) Date: Sun, 2 Jan 2011 00:46:11 +0100 From: marco To: freebsd-ports@freebsd.org Message-ID: <20110101234611.GA14606@lordsith.net> Mail-Followup-To: marco , freebsd-ports@freebsd.org References: <4D1F7DEA.9020006@FreeBSD.org> <4D1F889B.6050500@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D1F889B.6050500@FreeBSD.org> Organization: LordSith.Net X-Operating-System: FreeBSD 9.0-CURRENT X-Unix: Use UNIX or Die X-GPG-Fingerprint: A025 D8AA AC1B D2FC 380D 4FC1 8EA0 0BA8 8580 E6CB X-GPG-Key: http://lordsith.net/gpgkey X-dmesg-current: http://lordsith.net/trinity-ahci-dmesg.txt X-Uptime: 11:29PM up 16 days, 14:22, 5 users, load averages: 0.02, 0.07, 0.07 User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: ports-mgmt/portconf , ports-mgmt/portmaster and make args X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: marco List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 23:46:15 -0000 On Sat, Jan 01, 2011 at 12:03:39PM -0800, you (Doug Barton) sent the following to [freebsd-ports] : > On 01/01/2011 11:44, b. f. wrote: > > On 1/1/11, Doug Barton wrote: > >> On 12/31/2010 18:40, b. f. wrote: > >> > >>> You don't need to go to those lengths. You could just add a > >>> command-line switch, or a check for a cookie (.buildme or .nopkg, say) > >>> in the corresponding PORT_DBDIR subdirector(y|ies), or both, to allow > >>> the user to indicate to portmaster that it should always build the > >>> port(s) in question, even if -P is used. > >> > >> My preferences are for something that it's possible for other port tool > >> authors to use, and something that requires the minimal necessary steps > >> for the user. Since the OP is already editing knobs in ports.conf, and > >> since IMO either ports.conf or make.conf are easier to transport between > >> systems I think I'll give Matthew's idea a try first. :) I'll be eagerly awaiting the implementation. > > > > Whatever works, as long as it is not specific to ports-mgmt/portconf, > > because many users may not use that port and yet still want to avoid > > the use of packages for certain ports. Note that various Makefiles > > (Makefile.{inc,local,${ARCH},${OPSYS}, and ${ARCH}-${OPSYS}}) can also > > hold per-port defines that may have to be accounted for, > > Right, which is another reason that doing 'make -V > PT_NO_INSTALL_PACKAGE' at the /usr/ports/category/portname level seems > like a good way to go. > > > and that > > NO_PACKAGE may preclude your use of 'make package' with -g in > > portmaster (at least without some workaround like FORCE_PACKAGE). > > Different issue, the OP was concerned about using packages to install > all of his ports _except_ for the ones where he had defined options in > ports.conf. Correct. -- Regards, .marco. Use UNIX or die.