From: | teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) |
---|---|
To: | Justin Clift <aa2(at)bigpond(dot)net(dot)au> |
Cc: | lockhart(at)fourpalms(dot)org, Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RPM building (was regression on RedHat) |
Date: | 2001-03-22 00:43:08 |
Message-ID: | xuyn1ae1vmr.fsf@halden.devel.redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Justin Clift <aa2(at)bigpond(dot)net(dot)au> writes:
> It's not "Mandrake" that will be broken. Mandrake is also often used by
> new Linux users who wouldn't have the slightest idea about setting GCC
> options. It'll be THEM that have broken installations if we take this
> approach (as an aside, that means that WE will be probably also be
> answering more questions about PostgreSQL being broken on Mandrake
> systems).
>
> Isn't it better that PostgreSQL works with what it's got on a system AND
> ALSO that someone notifies the Mandrake people regarding the problem?
Most people will use what the vendor ship - a vendor (like us) look
into the benefits (stability, performance, compatiblity) of different
packages, and make a selection. If they've done a choice of which
options are used in their distribution, they are obviously fine with
the consequences.
--
Trond Eivind Glomsrød
Red Hat, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Steven Vajdic | 2001-03-22 01:03:16 | Migration - Linux/pgSQL/PHP (type,version) |
Previous Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-03-22 00:31:13 | Re: Call for platforms (linux 2.4.x ?) |