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 <guix-devel@gnu.org>
Subject: Re: 01/03: gnu: hurd: Add hurd-kernel-headers package.
Date: Wed, 26 Aug 2015 13:03:17 +0200	[thread overview]
Message-ID: <87h9nm9uru.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzPtcbuV=ZYtrgwCjyTjCRSRfv4wjmaDA-CAmfPb3ie7yA@mail.gmail.com> (Manolis Ragkousis's message of "Tue, 18 Aug 2015 14:13:23 +0300")

Manolis Ragkousis <manolis837@gmail.com> skribis:

> We discussed that a union package could be helpful to avoid having to
> handle 3 packages every time,
> plus make it easier to choose between linux and hurd headers.

Yes, I remember that.

What I wonder though is whether we can achieve the same thing as the
union but using propagated inputs instead.

> Adding hurd-minimal as an input to hurd-headers will create dependency
> problems, because hurd-minimal inherits hurd-headers.

Yes, but that’s OK (the ‘inputs’ field is “thunked”, so it can contain
references to not-yet-defined variables.)

> I can solve that, but I believe the union package to be a much simpler approach.

I think propagated inputs would make things simpler since that would
allow us to remove the code that builds the union.

But it could be that I’m overlooking something, or that it wouldn’t work
for some obscure reason.

Could you give it a try to see what happens?

TIA!

Ludo’.

      reply	other threads:[~2015-08-26 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150811133830.13025.5100@vcs.savannah.gnu.org>
     [not found] ` <E1ZP9l8-0003P1-RL@vcs.savannah.gnu.org>
2015-08-18 10:56   ` 01/03: gnu: hurd: Add hurd-kernel-headers package Ludovic Courtès
2015-08-18 11:13     ` Manolis Ragkousis
2015-08-26 11:03       ` Ludovic Courtès [this message]

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=87h9nm9uru.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.