From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Reminder on dependencies.
Date: Tue, 25 Oct 2005 11:55:45 -0500 [thread overview]
Message-ID: <20051025165545.GG23614@bmb24.uth.tmc.edu> (raw)
In-Reply-To: <435DFAB1.90603@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
Donnie Berkholz wrote: [Tue Oct 25 2005, 04:28:17AM CDT]
> I'm still failing to see how headers have anything to do with runtime
> issues -- it should be people's responsibility to ensure they have the
> necessary headers if they're compiling things that require them. And
> compiling means DEPEND.
It's possible that I'm being particularly dense today, but at least at
the moment it seems fairly simple to me. DEPEND means that portage
requires the dep for the current package to build successfully.
RDEPEND, on the other hand, lists dependencies that users of a package
will need down the road, after it's installed on the system. So, for
example, libfoo might not require that boost be installed for it to
build, but libfoo might export a header file that imports
boost/tuple.hpp. If boost isn't in libfoo's RDEPEND, then when user
Fred installs libfoo from a binary package and tries to use libfoo's
header files in development, a rude shock is likely.
> Maybe for some people compiling is included in runtime, but I'm not one
> of them.
I am. I frequently compile software against installed libraries in my
day job. I don't run into this problem solely because I don't install
binary packages.
My apologies if I'm missing the point here.
-g2boojum-
--
Grant Goodyear
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0 9573 A6DC 7152 E0F6 5B76
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-25 16:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 0:18 [gentoo-dev] Reminder on dependencies Spider (D.m.D. Lj.)
2005-10-25 4:37 ` Donnie Berkholz
2005-10-25 5:12 ` Joshua Baergen
2005-10-25 5:18 ` Ned Ludd
2005-10-26 8:46 ` Paul de Vrieze
2005-10-25 5:29 ` Spider (D.m.D. Lj.)
2005-10-25 5:51 ` Donnie Berkholz
2005-10-25 6:01 ` Spider (D.m.D. Lj.)
2005-10-26 8:45 ` Paul de Vrieze
2005-10-25 7:49 ` Thomas de Grenier de Latour
2005-10-25 12:15 ` Ciaran McCreesh
2005-10-25 14:09 ` Donnie Berkholz
2005-10-25 16:03 ` John Myers
2005-10-25 16:39 ` Ciaran McCreesh
2005-10-25 10:48 ` Donnie Berkholz
2005-10-25 17:55 ` solar
2005-10-25 19:16 ` Ciaran McCreesh
2005-10-25 19:28 ` Olivier Crete
2005-10-25 20:05 ` solar
2005-10-25 20:38 ` Ciaran McCreesh
2005-10-26 8:58 ` Paul de Vrieze
2005-10-27 0:15 ` Luca Barbato
2005-10-27 7:36 ` Paul de Vrieze
2005-10-27 13:40 ` Olivier Crête
2005-10-27 14:14 ` Ned Ludd
2005-10-25 16:19 ` Grant Goodyear
2005-10-25 9:28 ` Donnie Berkholz
2005-10-25 16:41 ` Ciaran McCreesh
2005-10-25 17:16 ` Joshua Baergen
2005-10-25 17:25 ` Ciaran McCreesh
2005-10-25 17:37 ` Joshua Baergen
2005-10-25 17:41 ` Joshua Baergen
2005-10-25 17:44 ` Alec Joseph Warner
2005-10-25 17:55 ` Ciaran McCreesh
2005-10-25 16:55 ` Grant Goodyear [this message]
2005-10-26 9:04 ` Paul de Vrieze
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051025165545.GG23614@bmb24.uth.tmc.edu \
--to=g2boojum@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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