From owner-freebsd-ports@FreeBSD.ORG Wed Apr 14 16:08:27 2004 Return-Path: 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 E1C0216A4CF for ; Wed, 14 Apr 2004 16:08:27 -0700 (PDT) Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBC8843D31 for ; Wed, 14 Apr 2004 16:08:27 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (5da2a07fa57f0a354c532a8c5034b0ff@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128])i3EN8Kt5025784; Wed, 14 Apr 2004 16:08:21 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 912F753A08; Wed, 14 Apr 2004 16:08:20 -0700 (PDT) Date: Wed, 14 Apr 2004 16:08:20 -0700 From: Kris Kennaway To: Garance A Drosihn Message-ID: <20040414230820.GB56438@xor.obsecurity.org> References: <20040413121925.GB29867@voodoo.oberon.net> <20040413121925.GB29867@voodoo.oberon.net> 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: freebsd-ports@freebsd.org Subject: Re: Second "RFC" on pkg-data idea for ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2004 23:08:28 -0000 --dc+cDN39EJAMEtIO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 14, 2004 at 04:15:51PM -0400, Garance A Drosihn wrote: > At 1:33 PM +0200 4/14/04, Dirk Meyer wrote: > >Garance A Drosihn schrieb:, > > > >> I wasn't looking for XML per se, so much as just something that > >> would be easy for a program to process. This should allow for > >> pretty arbitrary text for the values of each section, in the > >> same way that the present plain-files would accept anything. > >> No need for \'s to escape double-quote characters, or worries > >> about embedded ${} or any other characters which might be > >> special to make or to /bin/sh. > > > >A Makefile is very easy to process. > >We have all the tools for this. >=20 > I noticed how easy it was when the pkg-comment -> COMMENT > change broke the ports tree. That's exactly what got me > thinking about this project in the first place. >=20 > I'm sorry, but I really don't think it's the right format for > storing and manipulating arbitrary data. Yes, you can pound > any value into make variables if you hammer hard enough, but > for some kinds of (arbitrary) data I (personally) think it's > too much effort for too little reward. You have to compare one-time effort in making the transition with ongoing effort in using a more difficult system. Kris --dc+cDN39EJAMEtIO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAfcRkWry0BWjoQKURAk3YAJ9fnDYa2FWZKZNQUSKTCw64aG0KAACfbvBf J21TfwS+4we++TpwomPa0So= =XBCW -----END PGP SIGNATURE----- --dc+cDN39EJAMEtIO--