From owner-freebsd-java@FreeBSD.ORG Thu May 1 09:49:41 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12E2137B401; Thu, 1 May 2003 09:49:41 -0700 (PDT) Received: from puget.esil.univ-mrs.fr (puget.esil.univ-mrs.fr [139.124.41.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C82F43F3F; Thu, 1 May 2003 09:49:39 -0700 (PDT) (envelope-from herve.quiroz@esil.univ-mrs.fr) Received: from puget.esil.univ-mrs.fr (localhost.esil.univ-mrs.fr [127.0.0.1]) h41GmebJ093667; Thu, 1 May 2003 18:48:40 +0200 (CEST) (envelope-from herve.quiroz@esil.univ-mrs.fr) Received: from localhost (rv@localhost)h41Gma3T093664; Thu, 1 May 2003 18:48:39 +0200 (CEST) X-Authentication-Warning: puget.esil.univ-mrs.fr: rv owned process doing -bs Date: Thu, 1 May 2003 18:48:36 +0200 (CEST) From: Herve Quiroz X-X-Sender: rv@puget.esil.univ-mrs.fr To: Greg Lewis In-Reply-To: <20030501155811.GA78184@misty.eyesbeyond.com> Message-ID: <20030501182907.K83285@puget.esil.univ-mrs.fr> References: <200210140852.g9E8qfbH050638@zaphod.euronet.nl> <200305010918.56072.znerd@FreeBSD.org> <20030501155811.GA78184@misty.eyesbeyond.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Ernst de Haan cc: freebsd-java@FreeBSD.ORG Subject: Re: java/44041: Generate bsd.java.mk from an XML file X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 16:49:41 -0000 Hi Greg, On Thu, 1 May 2003, Greg Lewis wrote: > On Thu, May 01, 2003 at 09:18:56AM +0200, Ernst de Haan wrote: > > Hi Herve, > > > > > I was in the mood for some XSLT coding so I decided to take care of this > > > one hour ago. So far, I've finished everything up to step 3 (included) > > > but I will need to get some sleep sooner or later ;) > > > > > > So I was wondering if you still need this XML->bsd.java.mk tool... and if > > > you (or anybody else) had already done something about it. > > > > Haven't done anything about it yet. And I personally think it's a very good > > idea. This way we only have to maintain a bsd.java.xml file. > > > > Greg, what do you think of this? > > Well, without having seen Herve's XSLT, I think the best way of explaining > things is to describe what I would like to see ultimately happen with > bsd.java.mk. Maybe some of this is due to not fully understanding the > file, but here goes. > [...] > Well, I was just working on the dependency stuff in stage 4 of the bsd.java.mk which is not simple to implement in XSLT. But maybe I should wait that we fix this before... You're right bsd.java.mk sometimes behaves a strange way. And your "multiple JDK dependency" point is right if you take for example the jakarta-commons-logging port. It compiles and runs with any JDK (1.2+) but if you've got JDK 1.4, it's better because it also handles the 1.4 logger API. the jakarta-commons-logging is bugged (log4j dependency) but I am fixing it ATM and will send a PR is the next few minutes. So, the question is: what to do for now ? Let the bsd.java.mk as-is ? Have an XSLT to generate it from an XML Java VMs list ? We could have a user/system configuration file to specify which JDKs/JREs to install and in which order, as it is the case for many applications (/usr/local/etc/pkgtools.conf, /etc/make.conf...). And to be "cutting-edge", we could use an XML file to store preferences instead of the standard Perl or Ruby stuff. XML processing has many dependencies but so does any Java port so this is not an issue. What are the opinions of other Java porters ? Regards, Herve Ernst, you're fast at commiting port updates. Thanks ! :)