From owner-freebsd-ports@FreeBSD.ORG Mon Feb 14 09:19:32 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A83A16A4CE; Mon, 14 Feb 2005 09:19:32 +0000 (GMT) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 629A643D39; Mon, 14 Feb 2005 09:19:31 +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 6920F4AC3A; Mon, 14 Feb 2005 10:19:29 +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 51083-01-30; Mon, 14 Feb 2005 10:19:29 +0100 (CET) Received: from [192.168.1.187] (81.milagro.bahnhof.net [195.178.168.81]) by melon.pingpong.net (Postfix) with ESMTP id 40E754AC35; Mon, 14 Feb 2005 10:19:29 +0100 (CET) Date: Mon, 14 Feb 2005 10:19:25 +0100 From: Palle Girgensohn To: Panagiotis Astithas Message-ID: <408B661F5EDB9C3D9623E3E5@rambutan.pingpong.net> In-Reply-To: <42106C38.6060006@ebs.gr> References: <42106C38.6060006@ebs.gr> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net cc: ports@freebsd.org cc: java@freebsd.org Subject: Re: postgresql-jdbc packaging X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Feb 2005 09:19:32 -0000 --On m=E5ndag, februari 14, 2005 11.15.36 +0200 Panagiotis Astithas=20 wrote: > Palle Girgensohn wrote: >> 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 =3D> >> JDBC1, jdk1.2-1.3 =3D> JDBC2, and jdk1.4+ =3D> 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=3D1.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.) > > As someone who was bitten by this, I believe package users should have > some sort of warning sign. I don't mind what the solution will be, as > long as a regular "pkg_add -r foo" can work as expected. Is this possible > with the "slimmer" approach? > > Cheers, > > Panagiotis With the slimmer approach, pkg_add will install postgresql-jdbc1,=20 explicitally. With the fatter approach, there will be three packages to=20 chose from, one each for jdbc{1,2,3}. /Palle