From owner-freebsd-java@FreeBSD.ORG Fri Mar 12 09:57:42 2004 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 F1BA816A4D2 for ; Fri, 12 Mar 2004 09:57:41 -0800 (PST) Received: from arabica.esil.univ-mrs.fr (arabica.esil.univ-mrs.fr [139.124.41.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AB6243D41 for ; Fri, 12 Mar 2004 09:57:41 -0800 (PST) (envelope-from herve.quiroz@esil.univ-mrs.fr) Received: from arabica.esil.univ-mrs.fr (localhost.esil.univ-mrs.fr [127.0.0.1])i2CHvdGQ006224; Fri, 12 Mar 2004 18:57:39 +0100 (CET) (envelope-from herve.quiroz@esil.univ-mrs.fr) Received: (from rv@localhost)i2CHvcBY006223; Fri, 12 Mar 2004 18:57:38 +0100 (CET) (envelope-from herve.quiroz@esil.univ-mrs.fr) X-Authentication-Warning: arabica.esil.univ-mrs.fr: rv set sender to herve.quiroz@esil.univ-mrs.fr using -f Date: Fri, 12 Mar 2004 18:57:38 +0100 From: Herve Quiroz To: Gabriel Ambuehl Message-ID: <20040312175738.GA6099@arabica.esil.univ-mrs.fr> Mail-Followup-To: Gabriel Ambuehl , Manfred Riem , freebsd-java@FreeBSD.ORG References: <20040308153418.GA33232@arabica.esil.univ-mrs.fr> <1226113013.20040309141947@buz.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1226113013.20040309141947@buz.ch> User-Agent: Mutt/1.4.2.1i cc: Manfred Riem cc: freebsd-java@FreeBSD.ORG Subject: Re: PKGNAMEPREFIX for Java ports 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: Fri, 12 Mar 2004 17:57:42 -0000 Hi Gabriel, On Tue, Mar 09, 2004 at 02:19:47PM +0100, Gabriel Ambuehl wrote: > I think it's not so bad to have Java ports in the java directory > considering what PITA it is to build Java (even on a fast machine, it > takes forever and that's only the tip of the ice berg). This way people might > be more aware of the fact that they'll need to go through the linux emu > hoops to get it working... I mean the scripting languages are built > quickly on any reasonably current hardware. I'm not sure I understand your point of view here... are you speaking of JDK ports or all Java ports? I didn't state anything regarding JDKs but if you ask me, I think if we get rid of Java ports from the 'java' directory, we could also move JDK ports towards another directory (probably 'lang' IMHO). Anyway, regarding Java ports, I agree there should be a way to quickly (and simply) identify that a port needs Java to build and/or run. And that's the main point of my original message: "How to name and where to put a Java port, still preserving FreeBSD category/directory rules but with an apparent 'java' tag?". Basically, the question may be: 'java/portname' or 'category/java-portname'? Do you suggest that the 'java-' prefix in the port directory name will not be enough? Actually I was thinking that it would produce some opposite effect when I posted my message. Indeed, if I am to install 'fop' (which name does not sound like Java, as there is no 'J' in it), a simple 'portupgrade fop' would be enough. So the use of Java is not obvious. FOP is actually a recommended tool to handle XSL-FO. So unaware users may give it a try and then get surprised with all that work and stuff needed to install it. Having to execute 'portupgrade java-fop' would make sure that users are aware of the java dependency. Still the port would be located in a directory relative to its category ('textproc' as for any text processing tool), which would be considered the "right" place for any non-Java port. As a side note, we already have a native binary distribution for JDK 1.3 and I believe that we will soon have the same for JDK 1.4, thanks to Alexey, Greg and others... So running Java won't be a PITA anymore. Thanks for your feedback. Herve