Date: Fri, 7 Feb 2003 21:06:46 -0800 From: Sean Chittenden <sean@chittenden.org> To: The Hermit Hacker <scrappy@hub.org> Cc: Edwin Groothuis <edwin@mavetju.org>, girgen@pingpong.net, ports@freebsd.org Subject: Re: databases/postgresql7-client port Message-ID: <20030208050646.GK15936@perrin.int.nxad.com> In-Reply-To: <20030208010148.M31303@localhost> References: <20030208035050.GA73243@k7.mavetju> <20030208045059.GJ15936@perrin.int.nxad.com> <20030208010148.M31303@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I was thinking today, after mistakingly installing the postgres7 > > > port without the WITHOUT_SERVER option, if it wouldn't be > > > handier to have a databases/postgresql7-client port to which all > > > the other ports refer if they need libpq.so.n as a dependency. > > > > Palle and I have turned this discussion over a few times now. > > What we concluded was that it'd be handy to have, but that the > > place to attack this problem would be on the PostgreSQL side of > > things and see if we can't work with the PostgreSQL developers to > > get them to assist in splitting up the tarballs or the > > distributions/targets so that it's easier to handle for everyone, > > not just FreeBSD. > > Actually, as one that has been spearheading this on the PostgreSQL > side of things, we've split things about as far as they can go > ... the 'client side' stuff is libpq and associated headers, which > are so tightenly tied with the backend code itself that that is the > one thing we can't split off ... > > Everything else we've tried to pull out and put into > gborg.postgresql.org as a seperate project, since all they require > is libpq itself to be installed, but libpq is one thing that will > never get split out as a seperate tar ball ... or, rather, with > 'never' being such a harsh/strong word, it has a very low chance of > ever being split off, to be close to 'never' ... Hrm, alright. Thanks for saving me the time re: looking into doing this. :) I'll put something together for the ports side of things then. What are the odds of introducing a configure directive that'd prevent the server from being compiled? -sc -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030208050646.GK15936>