From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Reminder on dependencies.
Date: Wed, 26 Oct 2005 10:45:56 +0200 [thread overview]
Message-ID: <200510261046.04512.pauldv@gentoo.org> (raw)
In-Reply-To: <1130220115.544.5.camel@Darkmere.darkmere>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On Tuesday 25 October 2005 08:01, Spider (D.m.D. Lj.) wrote:
>
> actually, I'm not in agreement here. If I install libfoo, be it from
> binaries or source, I certainly expect to be able to use libfoo, and
> that includes being able to build software against it, things I work
> on myself, other sources, or sources from Gentoo.
>
> We can hack around the later by being fanatical with our own DEPEND
> tracking, for the other two, our tree will remain completely broken.
>
> This is a case where we, a source based distro, is actually a crappier
> development platform than any of the current binary distributions.
I agree with Spider here. DEPEND in package x to me means what is needed
to make x build. RDEPEND in package x means what is needed to use package
x. There are various uses of x. One is running said package, another one
is building some other package (say y) against it.
This last meaning (building y against x) might have been put in a separate
dependency variable. This however is not so usefull as we have the
current format. But putting that meaning in DEPEND would mean that
portage would certainly need to merge all build time dependencies of a
package x to merge y. As such packages like virtual/jdk, autoconf,
automake might be unneededly pulled in.
Paul
--
Paul de Vrieze
Researcher
Mail: pauldv@cs.ru.nl
Homepage: http://www.devrieze.net
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-10-26 8:52 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 [this message]
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
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=200510261046.04512.pauldv@gentoo.org \
--to=pauldv@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