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: Tue, 05 Feb 2013 17:50:12 +0100	[thread overview]
Message-ID: <87ehgur9h7.fsf@gnu.org> (raw)
In-Reply-To: <201302042328.11563.andreas@enge.fr> (Andreas Enge's message of "Mon, 4 Feb 2013 23:28:11 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> Am Montag, 4. Februar 2013 schrieb Ludovic Courtès:
>> Andreas Enge <andreas@enge.fr> skribis:
>> > A question related to my previous posting, but also of independent
>> > justification: Should we maybe implement somthing similar to the
>> > "depends" field of Debian packages?
>> What’s this?
>
> When A "depends on" B in debian jargon, then installing A automatically 
> also installs B. In our case, a user issuing "guix-package -i mpc" would 
> end up with gmp, mpfr and mpc in the profile.

OK.  That’s “user-environment-propagated-inputs”.  We could achieve that
by just changing guix-profile to install propagated inputs.  That’s
probably the right thing to do anyway.

[...]

>> Yes, but mpfr.h and gmp.h still need to be in the user’s CPATH, which
>> contains ~/.guix-profile/include.  So putting them in the user’s profile
>> seems unavoidable.
>
> Probably so; come to think of it, the cases where one wants to link against 
> a dynamic library, but not write source code using the headers, should be 
> really rare (linking a compiled program against a newer version of the 
> library would be a possible case, which is somewhat contrary to the guix 
> philosophy).

Yes.

>> I think you’re concerned about cluttering the user’s profile, right?
>
> Not really. I just wonder what we should do, and what a user would expect. 
> For instance, in debian, gcc depends on binutils and the glibc. So when you 
> install gcc, you also get the other two packages. Is this what we want or 
> not?

In the general case, I think so, yes.

Installing MPC should definitely install MPFR and GMP.

Similarly for Guile 2.0, whose public headers refer to libgc’s.

For GCC, the situation is more complicated, because GCC has a loose tie
to Binutils and libc.  For instance, it happily takes whichever ‘ld’
program is in $PATH.  It’s more closely tied to libc, though, because we
explicitly patch its spec strings to refer to it; so at least libc
should be a propagated input of GCC.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2013-02-05 16:51 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 [this message]
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
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=87ehgur9h7.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).