From: Julien Lepiller <julien@lepiller.eu>
To: Pierre Neidhardt <mail@ambrevar.xyz>,guix-devel@gnu.org
Subject: Re: Reducing LLVM closure size
Date: Fri, 12 Jun 2020 09:34:51 -0400 [thread overview]
Message-ID: <80AFA6B5-2FAD-40EE-8AF5-8783EA6BB8D9@lepiller.eu> (raw)
In-Reply-To: <87tuzgpgjv.fsf@ambrevar.xyz>
Le 12 juin 2020 09:19:48 GMT-04:00, Pierre Neidhardt <mail@ambrevar.xyz> a écrit :
>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! :)
Because building this one will also rebuild the other two, re-read the sentence carefully :)
llvm -> clang -> clang-toolchain
next prev parent reply other threads:[~2020-06-12 13:35 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
2020-06-12 13:34 ` Julien Lepiller [this message]
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=80AFA6B5-2FAD-40EE-8AF5-8783EA6BB8D9@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).