From owner-freebsd-current@FreeBSD.ORG Tue Apr 13 17:03:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9563016A4CE for ; Tue, 13 Apr 2004 17:03:59 -0700 (PDT) Received: from smtp.web.de (smtp07.web.de [217.72.192.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 595C643D54 for ; Tue, 13 Apr 2004 17:03:59 -0700 (PDT) (envelope-from nakal@web.de) Received: from [217.225.235.219] (helo=[217.225.235.219]) by smtp.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.101 #91) id 1BDXsc-0007VC-00; Wed, 14 Apr 2004 02:03:51 +0200 From: Martin To: Garance A Drosihn In-Reply-To: References: <20040413121925.GB29867@voodoo.oberon.net> <407C4035.8020609@ciam.ru> <1081896823.772.58.camel@klotz.local> Content-Type: text/plain Message-Id: <1081901028.772.72.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 14 Apr 2004 02:03:49 +0200 Content-Transfer-Encoding: 7bit Sender: nakal@web.de cc: FreeBSD Current Subject: Re: Second "RFC" on pkg-data idea for ports X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2004 00:03:59 -0000 Am Wed, den 14.04.2004 schrieb Garance A Drosihn um 1:22: > If it is easy for you to execute commands, then something > like: > > /bin/make -f /usr/ports/shells/bash2/Makefile -V PORTVERSION Try to imagine, I have to call this command a few hundred times while unfolding a category node in my tree view. :) > Would it be useful-enough if the pd-handling program > could spit out a true XML-formatted document, once we knew > what that was? I realize this is rather lame, but it would > allow us to keep this key program pretty small and simple. I think, XML is good for writing out things. You can simply use fprintfs to spit out the data. It is normal to do that. It would be a good idea to have a good DTD or a XML-schema to parse it later. Having this few things in mind, you can just start with a XML-prologue, then the DOCTYPE and then whatever you want (as long as it's well-formed and valid XML). > Well, at the moment I am *not* using XML... :-) Sorry for my English :) Martin