From: Andreas Enge <andreas@enge.fr>
To: bug-guix@gnu.org
Subject: Required packages
Date: Mon, 4 Feb 2013 19:52:22 +0100 [thread overview]
Message-ID: <201302041952.22425.andreas@enge.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
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?
For instance, programming with mpc also requires mpfr and gmp; in fact, the
first few lines of mpc.h read
#include "gmp.h"
#include "mpfr.h"
So it would make sense to automatically pull in gmp and mpfr when a user
installs mpc. As dicussed with Ludovic, this could be handled by the
"propagated-inputs" field of the package definition.
But it also would make sense to not use such an automatism. For instance,
thanks to libtool, the mpc shared library is perfectly usable without
installing mpfr into the user profile, as libmpc.la contains a pointer to
the mpfr package:
dependency_libs=' /nix/store/l0999b93cw0by4hcv6z5ykzwz0gw358x-
mpfr-3.1.1/lib/libmpfr.la /nix/store/ydxa85j3i21ac74dv0vbc6cxjjqpsfsv-
gmp-5.1.0/lib/libgmp.la -lm'
So a user who only wants to use a library and not develop with it may not
be interested in getting all the dependent headers in the user profile.
An obvious approach would be to split into library and devel packages, as
does debian. But I do not think we should go this road, it is quite
convenient to get all of mpc in only one package.
What do you think?
Andreas
[-- Attachment #2: Type: text/html, Size: 4283 bytes --]
next reply other threads:[~2013-02-04 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 18:52 Andreas Enge [this message]
2013-02-04 22:08 ` Required packages 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
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=201302041952.22425.andreas@enge.fr \
--to=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).