unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: allan <allroj978@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Updating Packages
Date: Thu, 14 Jul 2022 13:28:23 +0300	[thread overview]
Message-ID: <867d4ggf94.fsf@bonfacemunyoki.com> (raw)
In-Reply-To: <c86931d418ea960066a53ffa5e7e08f0a88439e5.camel@gmail.com> (allan's message of "Tue, 12 Jul 2022 11:38:27 -0700")

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

allan <allroj978@gmail.com> anaandika:

> Hi there! I am new to software development, but I would like to contribute. I want to start by updating some rust packages to newer versions.<br>
>
> So far I have just been making scheme files in a seperate directory
> and running "guix build -f $SCHEME_FILE". I am trying to follow the
> [guidlines in the
> manual](https://guix.gnu.org/manual/en/html_node/Contributing.html),
> but git is still new to me and I am a little confused how to make this
> all work.
>
> What should I do to get package builds to recognize the updates I make to dependencies?
>

Have a look at:
<https://guix.gnu.org/cookbook/en/html_node/Packaging-Tutorial.html>
that has an in-depth take on packaging.  Once you
have a patch that you are ready to submit, follow
this:
<https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html>.
HTH'ed.

-- 
(Life is like a pencil that will surely run out,
    but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
    (hkp://keys.gnupg.net))

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

  reply	other threads:[~2022-07-14 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 18:38 Updating Packages allan
2022-07-14 10:28 ` Munyoki Kilyungi [this message]
2022-07-14 13:42   ` Josselin Poiret

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=867d4ggf94.fsf@bonfacemunyoki.com \
    --to=me@bonfacemunyoki.com \
    --cc=allroj978@gmail.com \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).