Contrib source

On Thu, 2011-06-30 at 10:46 -0400, gnuoytr@rcn.com wrote:

I'll need the contrib source, and I don't find it anywhere. I must not be looking in the right place.

Where might that be?

http://www.postgresql.org/ftp/source/

D'oh! I didn't recall that it was packaged together, but the contrib source isn't in src, where I looked. Oh well.

thanks,
Robert

---- Original message ----

On Thu, Jun 30, 2011 at 10:17 AM, <gnuoytr@rcn.com> wrote:

D'oh! I didn't recall that it was packaged together, but the contrib
source isn't in src, where I looked. Oh well.

IIt's not a separate file, there should be a contrib subdirectory in the
source code file.

However, if you're using a packaged pre-built binary, you're pretty much at
the mercy of the packager as to which contrib packages are built in (if any)
or available separately.

Using a pre-built binary and then building a contrib package from the source
code might cause some problems, I've always just built everything from the
source code.
--
Mike Nolan
nolan@tssi.com

I just got wholly confused. Synaptic makes it appear that *contrib is a separate entity. And the source isn't in a src subdirectory, but in the contrib directory directly. If I built PG on a regular basis, I might remember all this.

The xTuple folks only support a few PG releases, and with a specific set of modules built in. So, off to build it again.

Robert

---- Original message ----

On Thursday, June 30, 2011 9:48:57 am gnuoytr@rcn.com wrote:

I just got wholly confused. Synaptic makes it appear that *contrib is a
separate entity. And the source isn't in a src subdirectory, but in the
contrib directory directly. If I built PG on a regular basis, I might
remember all this.

Well contrib is just that, code that is not part of the core Postgres code, but
is contributed to the project. This is why it has its own directory. The src
directory is for the core Postgres code. Ubuntu packages the contrib code
separately for the same reason. The reason it installed the full Postgres code
is that the contrib modules cannot run without it and Synaptic had no way of
knowing about your existing self built code.

The xTuple folks only support a few PG releases, and with a specific set of
modules built in. So, off to build it again.

Robert

--
Adrian Klaver
adrian.klaver@gmail.com

On 07/01/2011 12:48 AM, gnuoytr@rcn.com wrote:

I just got wholly confused. Synaptic makes it appear that *contrib is a separate entity. And the source isn't in a src subdirectory, but in the contrib directory directly.

Debian, like most distros, produces several binary packages from a
single source package, so you can only install parts of it if you want.

It sounds like you installed the binary package for the contrib modules,
rather than downloading the source code.

If you'd used "apt-get source postgresql-8.4-contrib" (or whatever the
package name is) you would've found that the source package it
downloaded was just "postgresql-8.4".

If you "apt-cache show postgresql-8.4-contrib" you'll see that the
source package line will just show "postgresql-8.4" or something like
that, and will be the same for most of the other packages like the
client and server binary packages.

--
Craig Ringer

Yeah, I didn't realize that contrib source is in regular source download, nor did I notice that Synaptic was installing its own version of PG. The bulb wasn't lit. In all, I think I should have had two installs of PG; the one I built from source way back when (and stored out of standard location), and this one. It did, in fact build the standard version. The only reason I noticed was the perpetual error message about being unable to start PG due to some "server.key" not being found whenever the repository refreshed my machine. I figure that it should be able to start the one it built.

I just did a complete removal, and my home brew PG still works fine. I'll worry about adding contrib modules later.

Robert

---- Original message ----