Date: Sun, 15 Jun 2014 18:11:22 +0200 From: Kurt Jaeger <lists@opsec.eu> To: Matthew Seaman <matthew@FreeBSD.org> Cc: michelle@sorbs.net, freebsd-ports@freebsd.org Subject: Re: ports/189880: port pgpool-II out of date. Message-ID: <20140615161122.GB2586@home.opsec.eu> In-Reply-To: <539DB9DD.3050603@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140615161122.GB2586>