From: Caleb Ristvedt <caleb.ristvedt@cune.org>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 31836@debbugs.gnu.org
Subject: bug#31836: Installing bc downloads ghc
Date: Fri, 15 Jun 2018 08:00:09 -0500 [thread overview]
Message-ID: <CAELvotxqxq0C6tsq8e__DnV9YsrZyw5S3CK55ViMgVuLk=MRMQ@mail.gmail.com> (raw)
In-Reply-To: <87a7rwuw6m.fsf@mdc-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
I believe so. I think it's just ghc installed, though. Curiously enough, it
also went on to download mesa. Probably a similar mechanism at work there.
The only mention of hooks I see in the manual, though, is referring to the
daemon's build hook used for offloading. From what I see, though, I'd
assume that they are probably run in a way that errs on the side of "better
to run when unnecessary than not run when necessary".
This seems like a fairly common experience - "I ran foo and then it did
WHAT?". "guix graph" is really useful, but the parts that it can't explain,
it'd be nice to have documented. Where can I read more about these profile
hooks, that I may pursue this?
On Fri, Jun 15, 2018 at 6:27 AM, Ricardo Wurmus <
ricardo.wurmus@mdc-berlin.de> wrote:
>
> Hi Caleb,
>
> > Pretty much what the title says. I tried installing bc and it downloaded
> > ghc, among other things. I was curious how this came to be, so I ran […]
>
> I cannot reproduce this.
>
> Do you have other Haskell packages in your profile? This may be caused
> by the profile hook that is executed when building a new profile
> generation containing Haskell packages.
>
> --
> Ricardo
>
[-- Attachment #2: Type: text/html, Size: 1676 bytes --]
next prev parent reply other threads:[~2018-06-15 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 21:36 bug#31836: Installing bc downloads ghc Caleb Ristvedt
2018-06-15 11:27 ` Ricardo Wurmus
2018-06-15 13:00 ` Caleb Ristvedt [this message]
2018-06-16 20:55 ` Ricardo Wurmus
2018-06-17 4:56 ` Caleb Ristvedt
2018-06-15 13:34 ` 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
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='CAELvotxqxq0C6tsq8e__DnV9YsrZyw5S3CK55ViMgVuLk=MRMQ@mail.gmail.com' \
--to=caleb.ristvedt@cune.org \
--cc=31836@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).