unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: zimoun <zimon.toutoune@gmail.com>,
	47335@debbugs.gnu.org, Lars-Dominik Braun <lars@6xq.net>,
	ruppe.charlie@gmail.com
Cc: 47335-done@debbugs.gnu.org
Subject: bug#47335: Hide GHC not used for building Was: xmonad fails to recompile on guix system
Date: Wed, 15 Sep 2021 13:02:47 +0200	[thread overview]
Message-ID: <87v932rtig.fsf@yoctocell.xyz> (raw)
In-Reply-To: <CAJ3okZ2A5g41YcBF4SJ1=edcsk6GucqshVz2JSdhfkUcWy3U-Q@mail.gmail.com>

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

On Wed, Sep 15 2021, zimoun wrote:

> Hi,
>
> On Wed, 15 Sept 2021 at 09:43, Lars-Dominik Braun <lars@6xq.net> wrote:
>
>> > I'd be very much in favor of the latter, or maybe rename it to ghc-next.
>> > I have some profiles ghc pinned to a version and upgrading those is
>> > always a mess because Guix tries to build the old version from source
>> > instead of using the next version.
>>
>> I renamed ghc@8.8 to ghc-next in commit
>> 39b43d0d0428474a1d0bf58779d0135163b9c6e3.
>
> Well, I am late to the party and probably out of point but I think
> this '-next' is not something we should introduce and generalize.
> Well, who knows if these '-next' will be the real next. ;-)   My
> comment is also about guile-next, emacs-next and python-next.  Noting
> that gcc-toolchain does not have a '-next'; packages are built using
> 7.5.0 but "guix install gcc-toolchain" will install 11.2.0 and then it
> could lead to the same issue as the one reported with GHC, I guess.
>
> Instead of this '-next' trick, we should find a better mechanism where
> "guix install ghc" would install the default GHC used by the Haskell
> build-system.  Idem for the others guile-next, python-next etc..  And
> any other version should be installed using  the explicit mention,
> i.e., "guix install ghc@8.8", IMHO.

Agreed, but I guess using the ‘-next’ suffix was be the easiest
workaround for now.

Maybe running ‘guix install ghc’ should install the GHC package that the
‘ghc’ variable refers to.  Then this would not only apply to language
ecosystems, but all packages in general.  Right now running ‘guix
install rsync’ installs the ‘rsync-next’ package, but I would expect it
to install the package that the ‘rsync’ variable is bound to.

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

  reply	other threads:[~2021-09-15 11:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  0:13 bug#47335: xmonad fails to recompile on guix system Charlie Ruppe
2021-07-26  6:47 ` Lars-Dominik Braun
2021-08-01 17:51   ` bug#47335: Hide GHC not used for building Was: " raingloom
2021-09-15  7:42     ` Lars-Dominik Braun
2021-09-15  8:58       ` zimoun
2021-09-15 11:02         ` Xinglu Chen [this message]
2021-09-15  8:08           ` zimoun

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=87v932rtig.fsf@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=47335-done@debbugs.gnu.org \
    --cc=47335@debbugs.gnu.org \
    --cc=lars@6xq.net \
    --cc=ruppe.charlie@gmail.com \
    --cc=zimon.toutoune@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 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).