From owner-freebsd-ports@FreeBSD.ORG Wed Jun 7 03:17:53 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF84716A617; Wed, 7 Jun 2006 03:17:33 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A2D743D49; Wed, 7 Jun 2006 03:17:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 62DAE1A3C1C; Tue, 6 Jun 2006 20:17:33 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DFF7B515C6; Tue, 6 Jun 2006 23:17:32 -0400 (EDT) Date: Tue, 6 Jun 2006 23:17:32 -0400 From: Kris Kennaway To: Jiawei Ye Message-ID: <20060607031732.GB12014@xor.obsecurity.org> References: <4485DBF5.3070705@FreeBSD.org> <20060606211113.GA7845@xor.obsecurity.org> <20060607021330.GA11189@xor.obsecurity.org> <20060607022741.GA11522@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dc+cDN39EJAMEtIO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: Sergey Matveychuk , freebsd-ports@freebsd.org, Kris Kennaway Subject: Re: portupgrade ideas page 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, 07 Jun 2006 03:18:05 -0000 --dc+cDN39EJAMEtIO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 07, 2006 at 10:39:50AM +0800, Jiawei Ye wrote: > On 6/7/06, Kris Kennaway wrote: > >> If all customizations are to be done in make.conf, what is the point > >> of MAKE_ARGS in pkgtools.conf? > > > >Flexibility, it's not supposed to be the primary means of customizing > >your ports, that's make.conf's job. > > > >Kris > Eh, not supposed to be? I have to admit that this idea of > "correctness" is new to me. It's "correct" in the sense of "this is the way it was designed to work". portupgrade relies on the INDEX for computing dependencies, and the INDEX is a ports collection construct that uses ports collection resources including make.conf. > I have been using portupgrade since it > came into the ports tree. One thing I like about the > portupgrade/portmanager style of managing ports make_args is that they > provide a very simple syntax for specifying per-port args. > ''=3D>'arg1 arg2.....' (portupgrade style) > |arg1 arg2 arg3| (portmanager style) >=20 > Does make.conf provide such syntax? Last time I read from the ML, one > needs the {curdir} magic boiler plate for that. It is hard on the eyes > and reduces useful information on a 80x25 console IMHO. The latter. Kris --dc+cDN39EJAMEtIO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEhkVMWry0BWjoQKURAqFlAKCUxSK0vUAs3GL71kJEU8oLLSQ5fwCg+l8L RhGCpuBdfLvnSpCcKpxCFio= =jLCD -----END PGP SIGNATURE----- --dc+cDN39EJAMEtIO--