From: ludo@gnu.org (Ludovic Courtès)
To: dian_cecht@zoho.com
Cc: help-guix@gnu.org
Subject: Re: GuixSD installation: binary vs source packages
Date: Tue, 07 Mar 2017 11:59:51 +0100 [thread overview]
Message-ID: <87mvcxfj2w.fsf@gnu.org> (raw)
In-Reply-To: <20170306080914.1622ebc6@khaalida> (dian cecht's message of "Mon, 6 Mar 2017 08:09:14 -0800")
<dian_cecht@zoho.com> skribis:
> On Mon, 06 Mar 2017 11:59:51 +0100
> ludo@gnu.org (Ludovic Courtès) wrote:
>> However, in the presence of “grafts”, it may be that additional things
>> will be downloaded or built without you being notified beforehand.
>>
>> I consider this a bug but we don’t have an easy fix at this stage.
>
> Is there a number/link for that bug?
I realize there’s no explicit bug for that one, though it kind of
relates to <https://bugs.gnu.org/22990>.
Feel free to open a separate one!
Thanks,
Ludo’.
prev parent reply other threads:[~2017-03-07 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 18:39 GuixSD installation: binary vs source packages Alex Vestgaard
2017-02-25 2:01 ` myglc2
2017-02-25 15:52 ` Leo Famulari
2017-02-25 20:12 ` myglc2
2017-02-26 3:23 ` Leo Famulari
2017-03-06 10:59 ` Ludovic Courtès
2017-03-06 16:09 ` dian_cecht
2017-03-07 10:59 ` Ludovic Courtès [this message]
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=87mvcxfj2w.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dian_cecht@zoho.com \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).