unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Required packages
Date: Thu, 07 Feb 2013 22:39:36 +0100	[thread overview]
Message-ID: <87pq0bn6qv.fsf@gnu.org> (raw)
In-Reply-To: <201302071719.27034.andreas@enge.fr> (Andreas Enge's message of "Thu, 7 Feb 2013 17:19:26 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> Am Donnerstag, 7. Februar 2013 schrieb Ludovic Courtès:
>> Andreas Enge <andreas@enge.fr> skribis:
>> > In my attempt to install guix from guix, I came upon the problem that
>> > the libgcrypt headers require the libgpg-error headers. This is a
>> > propagated input, so should in the future be installed automatically.
>> The future is actually yesterday.  :-)
>
> Well, I first needed to compile yesterday's version, so my future was 
> indeed in the future (although now it is in the past, a fate every future 
> has to suffer). ;-)

I see.  Hopefully you don’t have to roll back to the future.  :-)

>> It’s a bit trickier.  linux-libre-headers is propagated by glibc, so if
>> you install glibc, you get both.
>> 
>> However, glibc is an /implicit/ input of everything that uses
>> ‘gnu-build-system’, such as libgcrypt.  So it doesn’t get installed when
>> you install libgcrypt.
>> 
>> I’m not sure whether glibc should be automatically installed as if it
>> were a propagated input.  If the answer were “yes”, I’m not sure how to
>> achieve it elegantly, because implicit inputs are hidden, by definition.
>
> Is this not too dangerous? It would mean that as soon as you install 
> anything, you get the glibc. And in a system that has guix and a native 
> glibc, things might stop working from there on...
>
> Since I installed the guix glibc before you implemented the automatic 
> installation of propagated inputs, I hit a problem that should have 
> disappeared in the meantime. So I would suggest to do nothing.

Yeah, I prefer it this way.

Thanks for the feedback,
Ludo’.

  reply	other threads:[~2013-02-07 21:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 18:52 Required packages Andreas Enge
2013-02-04 22:08 ` Ludovic Courtès
2013-02-04 22:28   ` Andreas Enge
2013-02-05 16:50     ` Ludovic Courtès
2013-02-05 23:09       ` Andreas Enge
2013-02-06 22:09       ` Ludovic Courtès
2013-02-07 12:16         ` Andreas Enge
2013-02-07 12:27           ` Andreas Enge
2013-02-07 16:08             ` Ludovic Courtès
2013-02-07 16:06           ` Ludovic Courtès
2013-02-07 16:19             ` Andreas Enge
2013-02-07 21:39               ` Ludovic Courtès [this message]
2013-02-07 12:34         ` Andreas Enge
2013-02-07 16:09           ` 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=87pq0bn6qv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=bug-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.
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).