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 <[email protected]> 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 >
