From owner-freebsd-java@FreeBSD.ORG Mon Feb 14 00:45:21 2005 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 42C7E16A4CE; Mon, 14 Feb 2005 00:45:21 +0000 (GMT) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0CE543D39; Mon, 14 Feb 2005 00:45:20 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id 96D5E4AC78; Mon, 14 Feb 2005 01:45:19 +0100 (CET) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13995-04; Mon, 14 Feb 2005 01:45:19 +0100 (CET) Received: from palle.girgensohn.se (1-2-8-5a.asp.sth.bostream.se [82.182.157.66]) by melon.pingpong.net (Postfix) with ESMTP id 5BD134AC33; Mon, 14 Feb 2005 01:45:19 +0100 (CET) Date: Mon, 14 Feb 2005 01:45:19 +0100 From: Palle Girgensohn To: ports@freebsd.org, java@freebsd.org Message-ID: X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net Subject: postgresql-jdbc packaging 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: Mon, 14 Feb 2005 00:45:21 -0000 Hi! I'm maintaining the postgresql-jdbc port. One thing I've considered, but not come to any conclusion about, is whether the port should register somehow which version of JDBC it has built, JDBC1, JDBC2 or JDBC3. There's even a JDBC2 + EE variant... Which version is built depends on which JDK was used to build it. jdk1.1 => JDBC1, jdk1.2-1.3 => JDBC2, and jdk1.4+ => JDBC3. Hence, very few would want JDBC1 nowadays, I suppose. The only package built by the package cluster now is for JDBC1, which kind of sucks a bit :) To fix this, the right way is to create a bunch of slave ports, on for each type as per above. Then, the package building cluster would build all version. The slave ports would set JAVA_VERSION=1.1 and 1.2 respectively, and the main port could install the greatest version. PKGNAMESUFFIX would be set to jdbcN. Is this just overkill? If most of you use the port anyway, it probably is, but if ppl tend to use prebuilt packages, they will end up with a somewhat crippled JDBC1 jar even if they run jdk-1.5, so then it might be worth it. I slimmer way is to just let the package name reflect which version has been built, but not bother to create slave ports. Any opinions? What do you think, is it worth the effort? /Palle (See for info on different versions of PostgreSQL's JDBC.)