From owner-freebsd-ports@FreeBSD.ORG Wed Apr 14 13:15:59 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 33C6F16A4CE for ; Wed, 14 Apr 2004 13:15:59 -0700 (PDT) Received: from smtp0.server.rpi.edu (smtp0.server.rpi.edu [128.113.53.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3C6E43D1F for ; Wed, 14 Apr 2004 13:15:58 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp0.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i3EKFqEd001256; Wed, 14 Apr 2004 16:15:55 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: <20040413121925.GB29867@voodoo.oberon.net> <20040413121925.GB29867@voodoo.oberon.net> Date: Wed, 14 Apr 2004 16:15:51 -0400 To: dirk.meyer@dinoex.sub.org (Dirk Meyer), freebsd-ports@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) 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 20:15:59 -0000 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. 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. 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. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu