Palle Girgensohn wrote:
So, apart from the obvious "I want to upgrade the client separately
(before) the server", there are no arguments for not doing it the way we
do it now. But maybe that argument is enough to motivate a change?
KIS is one reason we do not install clients with server (of ot
On Oct 17, 2014, at 10:44 AM, Palle Girgensohn wrote:
> Thing is, we install header files and man pages in the client only, if memory
> serves me right. Also, tools like createdb are in the client package.
>
> So, apart from the obvious "I want to upgrade the client separately (before)
> the
On Fri, Oct 17, 2014 at 04:44:47PM +0200, Palle Girgensohn wrote:
> Thing is, we install header files and man pages in the client only, if memory
> serves me right. Also, tools like createdb are in the client package.
>
> So, apart from the obvious "I want to upgrade the client separately (befor
Thing is, we install header files and man pages in the client only, if memory
serves me right. Also, tools like createdb are in the client package.
So, apart from the obvious "I want to upgrade the client separately (before)
the server", there are no arguments for not doing it the way we do it
In case the dependency on thr client will be removed all ports
depending on the server alone at the moment should be checked if they
also require the client part.
Additional clients should not define a conflict with server versions <
client version
--
Sent from my Android phone
Hi Dan,
Well, it has always been like that, actually.
PostgreSQL does not really support installing them completely separately.
PostgreSQL does support minimiziing the installation to the client only, but
not really the other way around. Maybe they are independent, I didn't really
check it ou
Hi Dan,
http://svnweb.freebsd.org/ports/head/databases/postgresql90-server/Makefile?revision=286930&view=markup#l64
It was always supposed to be the case, however I agree that it's probably not
necessary.
Anyone mind if it doesn't depend?
Chris
On 17 October 2014 15:12:51 BST, Dan Langille
