Date: Tue, 28 Jan 2025 16:35:12 +0100
From: Christoph Berg <myon@debian.org>
To: pgsqlitegis@tutamail.com
Cc: PostgreSQL in Debian <pgsql-pkg-debian@lists.postgresql.org>
Subject: Re: Redis & SQLite FDW packages
Message-ID: <Z5j5MLQpRuQpsqSd@msg.df7cb.de>
References: <OHgV4rO--F-9@tutamail.com>
 <Z5jc1WnEUfIwU-M9@msg.df7cb.de>
 <OHhPj4x--J-9@tutamail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <OHhPj4x--J-9@tutamail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/Z5j5MLQpRuQpsqSd%40msg.df7cb.de>
Precedence: bulk

Re: pgsqlitegis@tutamail.com
> I have absolutely no deb package expirience. I am confused about better way of packege creating. For example SQLite FDW supports PostgreSQL 11..17, x86 and arm architectures at least and 2 modes - with GIS support and without GIS support.
> For example there are possible
> pg 17 + GIS + x86
> pg 17 + GIS + arm
> pg 17 + GIS + ...
> pg 17 + noGIS + x86
> pg 17 + noGIS + arm
> pg 17 + noGIS + ...
> 
> pg 16 + GIS + x86

Is there any value in creating a separate "no GIS" variant? We usually
just enable all features.

Looping over the PG versions will be handled by pg_buildext in the
packaging toolchain. Looping over architectures is handled by invoking
that build separate on each architecture.

> MySQL FDW system of packages seems me ununderstandable and very hard.

Check any other extension then?

> By https://salsa.debian.org/postgresql/postgresql-common/-/blob/master/doc/postgresql-debian-packaging.md I think better 1st step is source code package, isn't it?

You create a source package (well, you create debian/ and then the
source package is built from that). From that, the binary packages are
built.

> I can prepare debian/control and something other debian/ files, but don't know anythink about PGDG apt package building infrastructure and metadata.

debian/ is all that is required.

Christoph