From: Mortimer Cladwell <mbcladwell@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: postgresql client packaging recipe
Date: Sat, 11 Dec 2021 06:35:08 -0500 [thread overview]
Message-ID: <CAOcxjM6FWGvHdDokoxcTEafbPRZ34VrgdNKZ097Fvdjy28NxCg@mail.gmail.com> (raw)
In-Reply-To: <87wnkc2fhv.fsf@nckx>
Thanks Tobias
You have updated my thinking about postgresql.
On Debian, apt-get install postgresql installs the postgres database/user
and starts the service. If you are distributing a client app (I am) and
you only want to provide the user with the psql executable (I do), then you
have the client install postgresql-client.
With guix, it looks like guix package -i postgresql does not by default
create a database/user and start the service, but does provide the psql
executable. Maybe I can provide the postgresql package without having to
worry about polluting the users desktop with db/user/service. That would
make postgresql-client redundant.
That is my current thinking. Correct me if I am wrong.
Thanks
Mortimer
On Fri, Dec 10, 2021 at 6:42 PM Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> Tobias Geerinckx-Rice 写道:
> >> Is there a protocol for submitting packaging recipes?
> >
> > There's no difference! :-)
>
> I might've been missing the spirit of the question here. Patches
> are the norm because they are easiest to review and commit.
>
> Stand-alone packages/recipes mean busywork for committers, who
> will be less likely to commit your package, or like you.
>
> But in practice, submitting your first package as stand-alone file
> to guix-patches@ or help-guix@ with a descriptive title is
> certainly not taboo. Someone will surely help you get both your
> package and your git set-up up to snuff.
>
> Kind regards,
>
> T G-R
>
prev parent reply other threads:[~2021-12-11 11:35 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
2021-12-10 23:30 ` Tobias Geerinckx-Rice
2021-12-11 11:35 ` Mortimer Cladwell [this message]
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=CAOcxjM6FWGvHdDokoxcTEafbPRZ34VrgdNKZ097Fvdjy28NxCg@mail.gmail.com \
--to=mbcladwell@gmail.com \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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).