From owner-freebsd-ports@FreeBSD.ORG Sat Nov 16 23:02:14 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1426AFA for ; Sat, 16 Nov 2013 23:02:14 +0000 (UTC) Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com [IPv6:2607:f2f8:a450::66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8622529F0 for ; Sat, 16 Nov 2013 23:02:14 +0000 (UTC) Received: from chombo.houseloki.net (unknown [IPv6:2601:7:1680:365:21c:c0ff:fe7f:96ee]) by yoshi.bluerosetech.com (Postfix) with ESMTPSA id A5B2AE606C; Sat, 16 Nov 2013 15:02:08 -0800 (PST) Received: from [IPv6:2601:7:1680:365:6948:f8a5:e3c:7d9d] (unknown [IPv6:2601:7:1680:365:6948:f8a5:e3c:7d9d]) by chombo.houseloki.net (Postfix) with ESMTPSA id 31F5BC32; Sat, 16 Nov 2013 15:02:07 -0800 (PST) Message-ID: <5287F96F.9070704@bluerosetech.com> Date: Sat, 16 Nov 2013 15:02:07 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Eitan Adler Subject: Re: Proposal for Authors / Vendors in ports References: <5283E4A0.6090107@pcbsd.org> <20131114073008.GG90670@droso.dk> <9D6E2358-4750-41D5-9B8C-F638C8B1E351@xs4all.nl> <5285CC00.6010800@FreeBSD.org> <5285DA85.3040008@freebsd.org> <5287CA4E.3070104@bluerosetech.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Nov 2013 23:02:14 -0000 On 11/16/2013 2:08 PM, Eitan Adler wrote: > On Sat, Nov 16, 2013 at 2:41 PM, Darren Pilgrim > wrote: >> On 11/16/2013 8:25 AM, Eitan Adler wrote: >> That's parseable using the regex or literal matching built into every >> scripting language, most programming languages, and your average human. > > Sure, but it requires extra tooling to make it work. I don't care > which file the data are stored in, I just > (a) don't want it to be free form > (b) want it to be in some standard format. > >> If >> you want to carry on about using an existing format, the above is CSV >> (character-separated values)--one of the most well-established and >> well-supported file formats in existence. > > Eh, the format proposed does not even come close to RFC 4180 (CSV). Heh. Pre-coffee brain failure. :) It is, however, the same format used for headers is pretty much everything.