all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "José Miguel Sánchez García" <jmi2k@openmailbox.org>, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: xmonad: Add missing propagated input.
Date: Wed, 11 Jan 2017 09:25:02 +0100	[thread overview]
Message-ID: <87ziiyypep.fsf@elephly.net> (raw)
In-Reply-To: <87r34ey21f.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> José Miguel Sánchez García <jmi2k@openmailbox.org> skribis:
>
>> xmonad package needs some love, and this is the first step. ghc should
>> be a
>> propagated input, because it's needed for certain commands such as
>> xmonad --recompile.
>
> Instead of propagating it, would it be possible to hard-code the
> absolute file name of ‘ghc’ inside the xmonad source?
>
> That would avoid pulling in GHC in the user’s profile, which could
> conflict with the user’s GHC.

Could we avoid all of this if we encouraged users to also install
whichever version of GHC they liked best?  Propagation seems bad here
and hard-coding a particular version of GHC in the store also doesn’t
quite seem right to me.

If a user wants to use a different GHC with libraries that are only
available with their particular version of GHC to reconfigure xmonad
then I think it’s best to just leave the decision up to the user.  The
user decides by installing their desired version of GHC into their
profile.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
http://elephly.net

      parent reply	other threads:[~2017-01-11  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 16:34 [PATCH] gnu: xmonad: Add missing propagated input José Miguel Sánchez García
2017-01-07 21:48 ` Ludovic Courtès
2017-01-07 22:28   ` José Miguel Sánchez García
2017-01-08 10:56     ` Ludovic Courtès
2017-01-09 16:28       ` José Miguel Sánchez García
2017-01-11  8:25   ` Ricardo Wurmus [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=87ziiyypep.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=jmi2k@openmailbox.org \
    --cc=ludo@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 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.