From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Required packages
Date: Wed, 06 Feb 2013 23:09:02 +0100 [thread overview]
Message-ID: <87bobxccxt.fsf@gnu.org> (raw)
In-Reply-To: <87ehgur9h7.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 05 Feb 2013 17:50:12 +0100")
Hi!
ludo@gnu.org (Ludovic Courtès) skribis:
> 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.
Commit 4dede02 implements that.
So now, when one installs MPC, MPFR and GMP automatically end up in the
profile as well. When removing MPC, all three vanish.
Of course, if you had installed MPC and MPFR (say), and then remove MPC,
MPFR and GMP remain in the profile. (IOW, it does the right thing.)
This required a slight change in the format of profile manifests, so
that the list of propagated inputs of each installed package is also
memorized.
Please test and report any issues!
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-02-06 22:09 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 [this message]
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=87bobxccxt.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).