From owner-freebsd-ports@FreeBSD.ORG Mon Apr 12 23:27:02 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 71BA016A4CE for ; Mon, 12 Apr 2004 23:27:02 -0700 (PDT) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id B873343D1F for ; Mon, 12 Apr 2004 23:27:01 -0700 (PDT) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.11/8.12.11) with ESMTP id i3D6R0cp064215; Tue, 13 Apr 2004 08:27:00 +0200 (CEST) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.11/8.12.11/Submit) id i3D6R08C064214; Tue, 13 Apr 2004 08:27:00 +0200 (CEST) (envelope-from stijn) Date: Tue, 13 Apr 2004 08:27:00 +0200 From: Stijn Hoop To: Garance A Drosihn Message-ID: <20040413062700.GA58667@pcwin002.win.tue.nl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! 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 06:27:02 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 12, 2004 at 11:40:59PM -0400, Garance A Drosihn wrote: > What I'd like is some idea of whether this project is worth > pursuing. Just a few comments from a quick drive-by reading: - it appears that your pkg-data format is in a language called Not Quite XML -- I think your longterm goal is worth it, so I'd suggest making it XML from the start - why not use separate sections (or did I miss that one)? - a tool to work with the pkg-data format with the options you describe is a must -- in fact I'd go so far as to say that I (as a ports maintainer) wo= uld like to test an implementation of it before I can say whether it doesn't disrupt my workflow too much. Just to give you an idea how I work: - At the start I compile my port, get a failure, add a patch, retry again - Then I check whether the software works, check the packaging, etc. Aga= in this is done by incrementally rebuilding etc. - When this is done I check pkg_add etc. I infer it should still be possible to compile a port without everything = in a pkg-data file because otherwise this would force me to add two invocati= ons of your tool before and after almost every step. I wouldn't mind having to run your tool before the packaging step because most of the time this just works (the port is nearly done anyway). In general I think it's an interesting idea. It depends on maintainer/commi= ter buy-in and a lot on the 'intrusiveness' of your changes wether it'll work though. HTH, --Stijn --=20 Man had always assumed that he was more intelligent than dolphins because he had achieved so much... the wheel, New York, wars, and so on, whilst all the dolphins had ever done was muck about in the water having a good time. But conversely the dolphins believed themselves to be more intelligent than man for precisely the same reasons. -- Douglas Adams, "The Hitchhikers Guide To The Galaxy" --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAe4g0Y3r/tLQmfWcRAtB5AKC2PufefwxO2Ox4SqMZmN31J5dQDgCff8lj CdmPThqV4/J7leRyxoGqT/E= =znxW -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--