Re: Redis & SQLite FDW packages
От | Christoph Berg |
---|---|
Тема | Re: Redis & SQLite FDW packages |
Дата | |
Msg-id | Z5j5MLQpRuQpsqSd@msg.df7cb.de обсуждение исходный текст |
Ответ на | Redis & SQLite FDW packages (pgsqlitegis@tutamail.com) |
Список | pgsql-pkg-debian |
Re: pgsqlitegis@tutamail.com > I have absolutely no deb package expirience. I am confused about better way of packege creating. For example SQLite FDWsupports 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 better1st 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 buildinginfrastructure and metadata. debian/ is all that is required. Christoph
В списке pgsql-pkg-debian по дате отправления: