Re: EnterpriseDB Postgres

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Dave Page <dpage(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-advocacy(at)postgresql(dot)org, Lukas Kahwe Smith <smith(at)pooteeweet(dot)org>
Subject: Re: EnterpriseDB Postgres
Date: 2007-08-08 16:37:00
Message-ID: 20070808163700.GF10513@svr2.hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-www

On Wed, Aug 08, 2007 at 09:30:28AM -0700, Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dave Page wrote:
> > Joshua D. Drake wrote:
> >> Dave Page wrote:
> >>> Peter Eisentraut wrote:
>
> > You were including server, admin tools and drivers in a point 'n' click
> > distro-independent installer? I thought Mammoth was a rebranded server
> > (now community standard).
>
> No it was a complete distribution. Not it was not point in click well
> except that you could use *standard* tools ;) such as yum/apt etc.. (we
> never did get yum working quite right).

I thought it was RPM only? Did it work on slackware for example?

> >> That is why we have so many packges in FC (for example now). Go Devrim!
> >
> > Absolutely - and we hope that will continue, just as I will be
> > continuing with pgInstaller.
> >
> > The EDB Postgres distros are aimed squarely at new users and those that
> > want a quick and easy install - we don't want them to have to understand
> > all the contrib module options in pgInstaller, or figure out the right
> > combinations of RPMs (not forgetting the libpq-compat one!),
>
> And breaking package management in the process. I am not trying to start

Uh, I haven't checked the installer on linux, but I was under the
impression that everything went in dedicated directory in /opt. How can
that break the package manager?

Sure you can't *use* the package manager - just like you acn't use it if
you install Oracle or DB2.

> a war here, but really, if it was done correctly you would have set up
> and apt server, a yum server etc... which is much more in line with the
> goal I would think.

I assume the whole package is directed at people who do not want to have to
reconfigure their yum/apt/whatever just to be able to try something out.

> > We want these users to just download, run and get hooked. Later, when
> > they decide to deploy, thats when they might choose to switch to the RPM
> > distros or pgInstaller, so they can tailor their production systems to
> > their precise needs.
>
> But that won't happen. Instead the users will be contained in the bubble
> that is the installer package (any not just EDB) and then when we say,
> download the latest RPMs, debs, use apt, use ports.. whatever, they go
> what? Please repeat.

I'd be very surprised if anybody who would go off and manually download the
binaries otherwise will use this distro. And I'd be surprised if users who
are used to using yum/apt/whatever will do that, they'll just use the one
they're used to. We're talking *new* users here.

(Though personally, I'd prefer a distro that doesn't mess around with the
packages like the debian one does for example. Not sure if this one fits,
but hey, I build from source all the time anyway)

//Magnus

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2007-08-08 16:37:28 Re: EnterpriseDB Postgres
Previous Message Peter Eisentraut 2007-08-08 16:36:44 Re: EnterpriseDB Postgres

Browse pgsql-www by date

  From Date Subject
Next Message Joshua D. Drake 2007-08-08 16:37:28 Re: EnterpriseDB Postgres
Previous Message Peter Eisentraut 2007-08-08 16:36:44 Re: EnterpriseDB Postgres