unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: help-guix <help-guix@gnu.org>
Subject: Process of adding a package
Date: Mon, 10 May 2021 09:43:54 +0000	[thread overview]
Message-ID: <fb0e2597-6cbc-9446-d69d-99d507f3cddf@posteo.de> (raw)

Hello Guix Users!

I have questions regarding the sending of patches and associated process of
releasing a package via GNU Guix:

What is the usual process, after one has sent in a patch adding a new package to
GNU Guix?

The background of the question is, that approximately 2 months ago, I sent in a
patch adding `guile-fslib`, but I don't know how long I should expect it to
take, until I can `guile pull` and `guix install <my newly added package>`.
Should I be worried, that it is not yet available? Did I do something wrong? Or
does it simply take some time, because someone needs to read the code of the
package I added, to verify, that nothing nefarious is going on?

Meanwhile I am using a git submodule instead, to use my library in my own
project and change the load path when starting my application, so that Guile
picks up the additional library. It would be great to be able to install it via
GNU Guix instead, avoiding the submodule thing completely.

Another, probably related question: When the package has been added, what is the
process behind updating the package? I send in a patch and then what happens? Is
it immediately updated, once some CI tests ran?

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl



             reply	other threads:[~2021-05-10  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  9:43 Zelphir Kaltstahl [this message]
2021-05-10 10:08 ` Process of adding a package Ricardo Wurmus
2021-05-10 15:46   ` Zelphir Kaltstahl
2021-05-10 16:14     ` Ricardo Wurmus

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=fb0e2597-6cbc-9446-d69d-99d507f3cddf@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=help-guix@gnu.org \
    /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).