From: solar <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Reminder on dependencies.
Date: Tue, 25 Oct 2005 13:55:36 -0400 [thread overview]
Message-ID: <1130262936.8910.63.camel@alto> (raw)
In-Reply-To: <20051025173956.0348f310@snowdrop.home>
On Tue, 2005-10-25 at 17:39 +0100, Ciaran McCreesh wrote:
> On Tue, 25 Oct 2005 07:09:03 -0700 Donnie Berkholz
> <spyderous@gentoo.org> wrote:
> | I disagree. You shouldn't expect to be able to compile things against
> | it unless all DEPENDs are installed. The whole point of DEPEND is to
> | be able to do things like this; remove all things not necessary for
> | your programs to run, not to compile.
>
> I'm glad to see you're volunteering to join in with Ned in going
> through every single ebuild in the tree and fixing them up to list nth
> level dependencies. It's going to be really fun watching you update
> several hundred packages every time a library's compile dependencies
> change between versions.
Please do not put words in my mouth. I've already asserted to you
several times that the definition of RDEPEND= is unclear and that we do
infact need a new set of depend atoms. R=(runtime) not Buildtime for the
NNth time. Till then please focus your efforts on something useful that
does not break other peoples systems or projects.
> See, if libfoo-1.0's headers don't need (say) boost, but libfoo-1.1's
> headers do, with what you're proposing you'd have to go through and
> update the dependencies of every single package using libfoo.
--
solar <solar@gentoo.org>
Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-25 18:03 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 [this message]
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=1130262936.8910.63.camel@alto \
--to=solar@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