public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ned Lilly <[email protected]>
To: Lamar Owen <[email protected]>
Cc: [email protected]
Cc: Robert Treat <[email protected]>
Cc: Lukas Kahwe Smith <[email protected]>
Subject: Re: PostgreSQL rebranding
Date: Tue, 29 Aug 2006 10:30:56 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

Lamar Owen wrote:
> On Tuesday 29 August 2006 07:50, Robert Treat wrote:
>> Postgres" which was recently offered by Pervasive.  I don't recall if Great
>> Bridge had such a repackaging, but someone else could probably chime in on
>> that. HTH.
> 
> Yes, Great Bridge did have their own packaging.  I can dig up the name; I did 
> the packages for them for 7.0.x a few years back as a consultant.  Hmm, 
> unless I'm remembering badly, it was simply 'Great Bridge PostgreSQL' and 
> they did very little modification from my packaging.  Tom Lane worked for 
> them around that time (late 2000).  The task was to develop 
> cross-distribution RPMs for TurboLinux, Caldera, SuSE, and RedHat/Mandrake.  
> That unfortunately didn't last long.... the Caldera OpenServer 2.3 RPM in 
> particular was very gnarly, being that Caldera was still using rpm 2.5.x 
> instead of a post 3.0 RPM, and they had redefined all the RPM macros...
> 
> My contact inside GB was Terry Carlin; initial contact was with Ned Lilly (who 
> is still around here somewhere; hi Ned!).
> 
> Wow, nice trip down memory lane as I read through my GreatBridge 
> correspondence archive... :-)

Hey Lamar.  Yeah, I responded to Lukas, but neglected to cc the list.  By his "fork" definition, the Great Bridge product wouldn't count.  It was in fact called Great Bridge PostgreSQL, and was basically some other stuff bundled with the 7.0 and 7.1 community server releases... RPM-i-fied by Lamar, as he says.

Cheers,
Ned

view thread (34+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PostgreSQL rebranding
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox