public inbox for [email protected]  
help / color / mirror / Atom feed
From: Devrim Gündüz <[email protected]>
To: John Harvey <[email protected]>
To: pgsql-pkg-yum <[email protected]>
Subject: Re: GDAL package naming question
Date: Mon, 26 Sep 2016 13:49:13 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABcP5fhUDt9SqywuHNm1uThEOL45YrddpO3RHmryW_01GexzOg@mail.gmail.com>
References: <CABcP5fhUDt9SqywuHNm1uThEOL45YrddpO3RHmryW_01GexzOg@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-pkg-yum>


Hi John,

On Wed, 2016-08-17 at 13:52 -0400, John Harvey wrote:
> 
> 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.

Right.

> 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

Right, they support only one version.

> 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)?

Well, I thought about adding suffix to gdal before, but then it might break
other packages that depend on versionless gdal.

Noone actually complained about it so far, so I *assumed* it is working. :-)

> 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.

Again, I did not hear any complaints from the field (yet), so... :)

Regards,

-- 
Devrim GÜNDÜZ
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR


Attachments:

  [application/pgp-signature] signature.asc (819B, 2-signature.asc)
  download

view thread (2+ messages)

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]
  Subject: Re: GDAL package naming question
  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