From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Julien Lepiller <julien@lepiller.eu>, guix-devel@gnu.org
Subject: Re: Reducing LLVM closure size
Date: Fri, 12 Jun 2020 15:19:48 +0200 [thread overview]
Message-ID: <87tuzgpgjv.fsf@ambrevar.xyz> (raw)
In-Reply-To: <898699F6-0111-41F0-826B-4A1C78F933EE@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
Julien Lepiller <julien@lepiller.eu> writes:
>>By the way, this looks like a bug:
>>
>>--8<---------------cut here---------------start------------->8---
>>> guix refresh -l llvm
>>Building the following package would ensure 3 dependent packages are
>>rebuilt: clang-toolchain@10.0.0
>>--8<---------------cut here---------------end--------------->8---
>>
>>Why is only 1 package displayed?
>
> Because these are the dependants for llvm@10, but the default llvm is llvm@9:
>
> guix refresh -l llvm@9
> Building the following 1180 packages would ensure 2092 lependent packages are rebuilt: …
This does not explain why it says "3 dependent packages" but lists only
one! :)
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-06-12 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 9:06 Reducing LLVM closure size Pierre Neidhardt
2020-06-12 12:01 ` Julien Lepiller
2020-06-12 12:09 ` Oliver Propst
2020-06-12 13:19 ` Pierre Neidhardt [this message]
2020-06-12 13:34 ` Julien Lepiller
2020-06-12 14:13 ` Pierre Neidhardt
2020-06-13 12:28 ` Arun Isaac
2020-06-13 15:34 ` Pierre Neidhardt
2020-06-16 9:22 ` Ludovic Courtès
2020-06-16 9:27 ` Pierre Neidhardt
2020-06-16 9:45 ` Efraim Flashner
2020-06-16 10:11 ` Pierre Neidhardt
2020-07-07 8:49 ` Pierre Neidhardt
2020-06-23 8:41 ` Pierre Neidhardt
2020-06-28 20:30 ` Ludovic Courtès
2020-07-28 10:09 ` Pierre Neidhardt
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=87tuzgpgjv.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).