From owner-freebsd-java@FreeBSD.ORG Wed Mar 26 03:57:59 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 3A71637B404 for ; Wed, 26 Mar 2003 03:57:59 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2049543F85 for ; Wed, 26 Mar 2003 03:57:57 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 18y9XQ-0004ZY-00 for freebsd-java@FreeBSD.org; Wed, 26 Mar 2003 13:57:48 +0200 Date: Wed, 26 Mar 2003 13:57:48 +0200 From: Sheldon Hearn To: freebsd-java@FreeBSD.org Message-ID: <20030326115748.GH9268@starjuice.net> Mail-Followup-To: freebsd-java@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn X-Spam-Status: No, hits=-6.4 required=5.0 tests=USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Java package distribution conventions 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: Wed, 26 Mar 2003 11:58:02 -0000 Hi folks, I see that it's something of a convention for open source Java package distributions to include all dependency JAR files. I can kinda see how this makes sense in terms of ease of deployment, but it's wasteful. I already have 27 copies of 15 flavours of ant.jar on my box! Do we already have a policy on handling this? There seem to be two current approaches. Some ports install into $PREFIX/share/java/classes, while others just install into $PREFIX/$DISTNAME. Approaches I can think of: 1) Ideal ======== The ideal solution is to have Java ports that only install the target package's JARs, and properly establish dependencies. This is how I'd like to do my ports. Obviously, that takes a LOT of work, and others may not be willing. 2) Status Quo ============= Perhaps the current system (port maintainers get to choose one of the two current approaches for each port) is good enough? If so, I'd at least like USE_JAVA to imply PREFIX=${JAVA_PREFIX} where the default would be JAVA_PREFIX?=${LOCALBASE} for backward compatibility or JAVA_PREFIX?=${LOCALBASE}/java for tidiness. Opinions? Ciao, Sheldon.