From owner-freebsd-ports@FreeBSD.ORG Tue Apr 13 06:32:12 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 E5B0916A4CE for ; Tue, 13 Apr 2004 06:32:12 -0700 (PDT) Received: from srv01.sparkit.no (srv01.sparkit.no [193.69.116.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42DE843D58 for ; Tue, 13 Apr 2004 06:32:12 -0700 (PDT) (envelope-from eivind@FreeBSD.org) Received: from ws ([193.69.114.88]) by srv01.sparkit.no (8.12.10/8.12.10) with ESMTP id i3DDW7cZ007381; Tue, 13 Apr 2004 15:32:08 +0200 (CEST) (envelope-from eivind@FreeBSD.org) Received: from ws (localhost [127.0.0.1]) by ws (8.12.9/8.12.10) with ESMTP id i3DDV27K004763; Tue, 13 Apr 2004 13:31:02 GMT (envelope-from eivind@ws) Received: (from eivind@localhost) by ws (8.12.9/8.12.10/Submit) id i3DDV2YE004760; Tue, 13 Apr 2004 13:31:02 GMT (envelope-from eivind) Date: Tue, 13 Apr 2004 13:30:01 +0000 From: Eivind Eklund To: Garance A Drosihn Message-ID: <20040413133000.GE2625@FreeBSD.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i 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: Tue, 13 Apr 2004 13:32:13 -0000 Please keep me in the Cc: list - I don't normally read ports@ On Mon, Apr 12, 2004 at 11:40:59PM -0400, Garance A Drosihn wrote: > The basic idea is to collapse many of the separate files for a > port into a single pkg-data file. The web pages explain why I > think this might be worth doing. Please check them out at: > > http://people.freebsd.org/~gad/PkgData/ There are two issues I immediately see (just to keep in mind during development): (1) The ability to do annotations and diffs on the patches themselves is fairly important. This ability can be kept even if they are assembled into a single file, but it requires that they are kept in a line-oriented format inside the assembled file. (2) If you do not use XML, you don't have to use a format that is "XML-like" - you can use e.g. significant indentation to make the format easier to read and edit. YAML (http://www.yaml.org) is an example of a markup format that is based on this, and gives much lighter (and thus easier to manually edit) markup. The ability to re-split the port into individual files for editing takes care of most other development issues, I think. Eivind.