Re: failed to install posgrest

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Eduardo Arévalo <earevaloch(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: failed to install posgrest
Date: 2004-01-04 15:48:20
Message-ID: 3FF835C4.9000402@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dave Page wrote:
> On Sat, Oct 4, 2008 at 12:36 AM, Joshua Drake <jd(at)commandprompt(dot)com> wrote:
>> Easy Dave. I was simply trying to figure out where the .bin came from,
>> which in turn came with a recommendation which I stand by that no one
>> should be using anything but operating supported packages (in this
>> case RPM, and assuming the package is available).
>
> Which, not all of it is, at least not from any source I'm aware of.

Well this list should not be supporting any of the modules that are non
postgresql anyway and I know all the postgresql packages are available
in native format.

>
>> I think it is also important to make a distinction that it is not
>> a .Org distributed file, so "if" there is a problem we can point the
>> user in the right direction to get help. Which may or may not be on
>> this list.
>
> Whether or not it's '.Org distributed' is irrelevant - I doubt you
> could help with a win32 installation problem for example. What is
> relevant, is the origin of the package, regardless of whether it came
> from the PostgreSQL ftp site.

I don't understand your point. The origin is EnterpriseDB, what does
that matter?

Joshua D. Drake

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Doug McNaught 2004-01-04 15:57:05 Re: Scripting a new db server setup
Previous Message Karsten Hilbert 2004-01-04 15:43:17 Re: Scripting a new db server setup