.deb source code package construction support

[mkgrgis]

PGDG apt support group propose me to try adding debian directory with content according official instruction to the repository. After some iterations we will can provide metadata for source code package, which will a base for a group of .deb packages, constructed on PGDG package factory for different processor architectures and PostgreSQL versions, with and without GIS support. Are pgspider team ready to review my PR about PGDG .deb support like @devrimgunduz support private rpm package construction process for the FDW?
There is accepted by PGDG and Debian team example of metadata files for other PostgreSQL extension.

[t-kataym]

@mkgrgis Thank you for your proposal.
But I'm sorry, this feature is low priority for us and we don't have enough time and knowledge to review it.

[mkgrgis]

But I'm sorry, this feature is low priority for us and we don't have enough time and knowledge to review it.

@t-kataym , what if all metadata from PR will be confirmed by official PostgreSQL development group (PGDG) maintainers? Our repo will be only full automated C code source for automated binary packaging for Debian and Ubuntu. All processes (with except for metadata updates) will be executed on official salsa servers of PGDG. I am also have no time for deep study of deb packages compilation, but maintainers explains me we need only metadata updating and some consultations.

Here is a PGDG draft after discussing with PGDG members: https://salsa.debian.org/bradfordboyle/sqlite-fdw

[mkgrgis]

@t-kataym , PGDG need official e-mail of code maintainer for including to standard .deb metadata. What should I answered?

[t-kataym]

I think there are 2 ways of thinking about e-mail.
One is a mail address of source code maintainer as you said, another is .deb package maintainer.
Which is suitable?

[mkgrgis]

I think there are 2 ways of thinking about e-mail. One is a mail address of source code maintainer as you said, another is .deb package maintainer. Which is suitable?

I think for changelog should be a mail address of source code maintainer, but for general metadata we need .deb package maintainer mail address.

[t-kataym]

for general metadata we need .deb package maintainer mail address.

Do you need this now?

[mkgrgis]

Do you need this now?

I think, yes.

This is a fragment from a review letter of Bradford Boyle, PGDG package member:

3. d/control

• The Maintainer field should be set to the package maintainer's
  name and email address [7]
  [7]: https://www.debian.org/doc/debian-policy/ch-controlfields.html#maintainer

debian/control is a well-documented file of general metadata. Also see https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer

[t-kataym]

I think your address is suitable in this case because PGSpider team does not maintain this repository .

[mkgrgis]

I think your address is suitable in this case because PGSpider team does not maintain this repository .

No problems, @t-kataym ! After special PR https://salsa.debian.org/bradfordboyle/sqlite-fdw will be precise copy of this repository. First Bradford Boyle should confirm debian metadata draft.

[mkgrgis]

There is yet compiled provided .deb packages https://pigsty.io/ext/fdw/sqlite_fdw/