all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Julien Lepiller <julien@lepiller.eu>
Cc: "39372@debbugs.gnu.org" <39372@debbugs.gnu.org>
Subject: [bug#39372] Chicken Scheme: Update version to 5.1.0 and add gcc-toolchain
Date: Sun, 09 Feb 2020 15:54:02 +0000	[thread overview]
Message-ID: <34Y0W0Ll0Mpsb3EexxFit46MyRTOblEmy9rRB5bwJbSzUx9Udyj4a4k55gDRn6r5JRgFs3YINo8MjKOs1pWCNGF4mQWRAreN6AQKO9tUDOQ=@elenq.tech> (raw)
In-Reply-To: <20200209153042.31f2d723@tachikoma.lepiller.eu>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, February 9, 2020 3:30 PM, Julien Lepiller <julien@lepiller.eu> wrote:

> This is almost correct. You should make it two patches: the first moves
> chicken to its own module, the second updates it. Make sure to add the
> licence in the new file with a copyright line for yourself. The commit
> message should be:
>
> gnu: chicken: Move to a separate module.
>
> -   gnu/packages/scheme.scm (chicken): Move to chicken.scm.
> -   gnu/packages/chicken.scm: New file.
> -   gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
>
>     for the first patch and:
>
>     gnu: chicken: Update to 5.1.0.
>
> -   gnu/packages/chicken.scm (chicken): Update to 5.1.0.
>     [propagated-inputs]: Add gcc-toolchain.
>
>     for the second patch. This makes it clearer what happens. You can find
>     a lot of examples from 'git log'.
>
>     Since no other package depends on chicken, we're all good I think.
>

Oh thanks.
I'll add them to the thread right now.

  reply	other threads:[~2020-02-09 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 16:22 [bug#39372] Chicken Scheme: Update version to 5.1.0 and add gcc-toolchain Ekaitz at ElenQ Technology
2020-02-01  0:36 ` Jonathan Brielmaier
2020-02-08 17:44 ` Julien Lepiller
2020-02-09 14:11 ` Ekaitz Zarraga
2020-02-09 14:30   ` Julien Lepiller
2020-02-09 15:54     ` Ekaitz Zarraga [this message]
2020-02-09 15:55       ` Ekaitz Zarraga
2020-02-09 15:55         ` Ekaitz Zarraga
2020-02-09 20:01   ` bug#39372: " Julien Lepiller
2020-02-09 20:03     ` [bug#39372] " Ekaitz Zarraga

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

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

  git send-email \
    --in-reply-to='34Y0W0Ll0Mpsb3EexxFit46MyRTOblEmy9rRB5bwJbSzUx9Udyj4a4k55gDRn6r5JRgFs3YINo8MjKOs1pWCNGF4mQWRAreN6AQKO9tUDOQ=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=39372@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.