From owner-freebsd-ports@FreeBSD.ORG Sat Nov 16 19:41:07 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 084B1E88 for ; Sat, 16 Nov 2013 19:41:07 +0000 (UTC) Received: from rush.bluerosetech.com (rush.bluerosetech.com [IPv6:2607:fc50:1000:9b00::25]) (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 D0BFC21C3 for ; Sat, 16 Nov 2013 19:41:06 +0000 (UTC) Received: from chombo.houseloki.net (c-71-236-222-167.hsd1.wa.comcast.net [71.236.222.167]) by rush.bluerosetech.com (Postfix) with ESMTPSA id B230B11491; Sat, 16 Nov 2013 11:41:04 -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 943BAC0D; Sat, 16 Nov 2013 11:41:01 -0800 (PST) Message-ID: <5287CA4E.3070104@bluerosetech.com> Date: Sat, 16 Nov 2013 11:41:02 -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> 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 19:41:07 -0000 On 11/16/2013 8:25 AM, Eitan Adler wrote: > On Sat, Nov 16, 2013 at 10:19 AM, Melvyn Sopacua wrote: >>> 2) If meta-information is moved to pkg-descr, it might be worthwhile >>> to add some knowledge about formats and restrictions to portlint. > > If we go this route I would *strongly* prefer that we do not invent > our own format. We should use an existing format. (I don't care > which one: YAML, JSON, ...) ? Which both require parsing libraries. We don't need that and neither does anything else that might want to read the ports tree and extract this information. This is easily implemented with simple keywords: We have "WWW:" in pkg-descr. So add "License:", "Vendor:", etc. to pkg-descr. That's parseable using the regex or literal matching built into every scripting language, most programming languages, and your average human. 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.