all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: glibc: Rename linux-headers input to kernel-headers.
Date: Tue, 19 Apr 2016 17:19:57 +0200	[thread overview]
Message-ID: <87mvop39sy.fsf@gnu.org> (raw)
In-Reply-To: <5710D9F9.8000404@gmail.com> (Manolis Ragkousis's message of "Fri, 15 Apr 2016 15:09:29 +0300")

Manolis Ragkousis <manolis837@gmail.com> skribis:

> Hey Ludo,
>
> On 04/14/16 00:07, Ludovic Courtès wrote:
>>> * gnu/packages/base.scm (glibc)[propagated-inputs]: Use a kernel
>>>   agnostic name for the kernel headers.
>>>   [arguments]: Adjust accordingly.
>>> * gnu/packages/commencement.scm (glibc-final-with-bootstrap-bash)
>>>   [propagated-inputs]: Adjust accordingly.
>> 
>> I think we also need to update the occurrences of ‘"linux-headers"’ in
>> cross-base.scm and make-bootstrap.scm, no?
>
>
> Well the occurrences of linux-headers in cross-base.scm and
> make-bootstrap.scm are not linked to the linux-headers input in
> base.scm. In both of those files the linux-headers input is replaced
> locally.

Those in make-bootstrap.scm definitely relate to base.scm (when doing
“guix build bootstrap-tarballs”), and the ones in cross-base.scm are not
entirely unrelated I think.

So I would prefer a mass rename.  Then we can apply it to core-updates
and be done with it.  :-)

WDYT?

Ludo’.

  reply	other threads:[~2016-04-19 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10 18:49 [PATCH] gnu: glibc: Rename linux-headers input to kernel-headers Manolis Ragkousis
2016-04-13 21:07 ` Ludovic Courtès
2016-04-15 12:09   ` Manolis Ragkousis
2016-04-19 15:19     ` Ludovic Courtès [this message]
2016-04-23 17:46       ` Manolis Ragkousis
2016-05-08 19:17         ` Ludovic Courtès

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=87mvop39sy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=manolis837@gmail.com \
    /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.