public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why ghc-bin is pulled in by portage update?
Date: Thu, 24 Sep 2015 07:38:36 -0400	[thread overview]
Message-ID: <20150924113836.GA4987@greenbeast> (raw)
In-Reply-To: <CA+t6X7eChz9UmtFG+D=5eEoN5Ck26kOSUwPjSaZdsGFQdGW2mA@mail.gmail.com>

On Thu, Sep 24, 2015 at 02:27:43PM +0300, gevisz wrote:
> I have dev-lang/ghc in my world file.
> 
> Today, while updating the system, the portage
> wanted to update it. Ok. But why it pulles in
> ghc-bin-7.8.4-amd64.tbz2?

Like all good language authors, the ghc authors wrote a lot of the
language and toolchain in Haskell, so you need a Haskell compiler to
compile ghc.

> >>> Downloading 'http://mirror.netcologne.de/gentoo/distfiles/ghc-bin-7.8.4-amd64.tbz2'
> --2015-09-24 14:12:02--
> http://mirror.netcologne.de/gentoo/distfiles/ghc-bin-7.8.4-amd64.tbz2
> Resolving mirror.netcologne.de... 194.8.197.22, 2001:4dd0:1234:1::deb
> Connecting to mirror.netcologne.de|194.8.197.22|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 100573133 (96M) [application/octet-stream]
> Saving to: '/usr/portage/distfiles/ghc-bin-7.8.4-amd64.tbz2'
> 
> /usr/portage/distfi 100%[=====================>]  95.91M   193KB/s   in 9m 54s
> 
> 2015-09-24 14:21:56 (165 KB/s) -
> '/usr/portage/distfiles/ghc-bin-7.8.4-amd64.tbz2' saved
> [100573133/100573133]
> 

There is a 'ghcbootstrap' USE flag that you can set to use your locally
installed ghc to build the new ghc.

Alec


  reply	other threads:[~2015-09-24 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 11:27 [gentoo-user] Why ghc-bin is pulled in by portage update? gevisz
2015-09-24 11:38 ` Alec Ten Harmsel [this message]
2015-09-24 11:50   ` gevisz

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=20150924113836.GA4987@greenbeast \
    --to=alec@alectenharmsel.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox