unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Mortimer Cladwell <mbcladwell@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: postgresql client packaging recipe
Date: Sat, 11 Dec 2021 00:21:17 +0100	[thread overview]
Message-ID: <871r2k3upu.fsf@nckx> (raw)
In-Reply-To: <CAOcxjM4uJvTXNgMBRbsc+L_3sS5fpOKRXr3hOd0mU0NbLALCaA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]

Mortimer,

> So I wrote a packaging recipe (below) and submitted to nonfree. 
> Was told
> it might be that no one has gotten around to packaging for main 
> yet.

Just FYI, Guix doesn't have sections like Debian.  There is only a 
single guix git repository, containing all packages supported and 
maintained by the Guix project.

Guix deals exclusively in Free software.  Any third-party 
repositories that don't follow the GNU Free Software Distribution 
Guidelines are not affiliated with GNU or Guix, and we can't 
provide support for them here.

I'm not aware of any licence issues with PostgreSQL, however, so 
we cool.

> I see
> the documentation for submitting patches, but not recipe 
> files. Is there a
> protocol for submitting packaging recipes?

There's no difference! :-)  Guix packages (=‘recipes’) are added 
to the repository as patches.  That's it.  Same as any other 
addition or fix: packages are just code, after all.

To submit a package upstream to Guix, you'd check out the git 
repository, add your package (‘recipe’) to a file that best suits 
it (here: databases.scm), commit it and send a patch as described 
in that section of the manual.

However…

>   (description "This package contains client and administrative 
>   programs
> for PostgreSQL: these are the interactive terminal client psql 
> and programs
> for creating and removing users and databases.")

…I'm a bit confused.  What exactly is missing?

λ ls $(guix build postgresql)/*bin
clusterdb          pg_config       pg_test_fsync
createdb           pg_controldata  pg_test_timing
createuser         pg_ctl          pg_upgrade
dropdb             pg_dump         pg_verifybackup
dropuser           pg_dumpall      pg_waldump
ecpg               pg_isready      postgres
initdb             pg_receivewal   postmaster
oid2name           pg_recvlogical  psql
pg_archivecleanup  pg_resetwal     reindexdb
pg_basebackup      pg_restore      vacuumdb
pgbench            pg_rewind       vacuumlo
pg_checksums       pg_standby

Sorry to be so dense.  I do use PostgreSQL but only know the very 
basics, I haven't even used or heard of most of those commands.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-12-10 23:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 21:41 postgresql client packaging recipe Mortimer Cladwell
2021-12-10 23:21 ` Tobias Geerinckx-Rice [this message]
2021-12-10 23:30   ` Tobias Geerinckx-Rice
2021-12-11 11:35     ` Mortimer Cladwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871r2k3upu.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=mbcladwell@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).