public inbox for [email protected]  

help / color / mirror / Atom feed

From: John Harvey <[email protected]>
To: pgsql-pkg-yum <[email protected]>
Subject: GDAL package naming question
Date: Wed, 17 Aug 2016 13:52:41 -0400
Message-ID: <CABcP5fhUDt9SqywuHNm1uThEOL45YrddpO3RHmryW_01GexzOg@mail.gmail.com> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-pkg-yum>

Hello folks,

I had a question about the GDAL package naming convention.
I noticed that PGDG will sometimes change the name of some packages in
order to include the version of postgres that they were compiled against
(or maybe that they require at runtime).  An example would be postgis2_95.

For reference, in the EPEL repo, PostGIS does not have the 95 modifier.
Here's a "yum list" result for postgis:
postgis.x86_64                          2.0.7-1.el7                    epel

I wanted to ask if there's a reason that GDAL didn't follow this
convention.  Even though each version of GDAL has a BuildRequires line that
specifies a pgmajorversion build dependency, the result isn't a gdal95 RPM.

Is the reason because there's no runtime dependency on postgres (just a
build one only)?

Also, if I used a version of gdal that was compiled with PostgreSQL 9.2
with my postgis2_95 build, would there be cause for concern?  With the "95"
off of the GDAL package name, it sort of implies that this sort of mixing /
matching would potentially be safe.  I'm guessing that's not the case, but
I figured it's worth asking.

Thank you!

Regards,
  -John Harvey

view thread (2+ 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]
  Subject: Re: GDAL package naming question
  In-Reply-To: <CABcP5fhUDt9SqywuHNm1uThEOL45YrddpO3RHmryW_01GexzOg@mail.gmail.com>

* 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