From owner-freebsd-ports@FreeBSD.ORG  Sun Jun 15 16:11:26 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 59946AEF;
 Sun, 15 Jun 2014 16:11:26 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 11D012741;
 Sun, 15 Jun 2014 16:11:26 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1WwD1e-0000o5-RU; Sun, 15 Jun 2014 18:11:22 +0200
Date: Sun, 15 Jun 2014 18:11:22 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Matthew Seaman <matthew@FreeBSD.org>
Subject: Re: ports/189880: port pgpool-II out of date.
Message-ID: <20140615161122.GB2586@home.opsec.eu>
References: <201405170220.s4H2K0G0085365@freefall.freebsd.org>
 <538D0AAE.7090800@sorbs.net> <20140615111101.GM2341@home.opsec.eu>
 <539DA4F3.2060004@sorbs.net> <20140615142903.GQ2341@home.opsec.eu>
 <539DB9DD.3050603@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <539DB9DD.3050603@FreeBSD.org>
Cc: michelle@sorbs.net, freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jun 2014 16:11:26 -0000

Hello,

> Heh.  I was just starting to look at writing a pgpool-II-33 port, but it
> seems you have beaten me to it.

Well, and you provided a thorough review, thanks for that!

Now, who's in charge to merge all your recommendations ? Michelle ?

> >>> Second step: merging the diverse set of pgpool related ports into one ?
> > 
> >> Maybe pg-pool-II and pg-pool-devel...?  (3.1/2 in stable and 3.3 in
> >> devel - until it changes?)
> 
> pgpool-II has 3 stable releases at the moment 3.1.10, 3.2.8, 3.3.3
> which are all still receiving updates.

Do you think that all three are still used by the ports users community ?

> > I assume that all the pgpool ports can be consolidated into one (3.3).

> > Maybe if we start by DEPRECATing the old ones to find out who
> > still wants them ? Bcc to kuriyama...

> There's a number of things wrong with this port, some inherited from the
> pgpool-II port you copied, and some where you're using outmoded constructs.
[lots of good hints]

-- 
pi@opsec.eu            +49 171 3101372                         6 years to go !