public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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:58:22 +0200	[thread overview]
Message-ID: <200510261058.22810.pauldv@gentoo.org> (raw)
In-Reply-To: <20051025213812.3ab52c01@snowdrop.home>

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

On Tuesday 25 October 2005 22:38, Ciaran McCreesh wrote:
> On Tue, 25 Oct 2005 16:05:00 -0400 solar <solar@gentoo.org> wrote:
> | You two are the ones trying to distort the meaning of RDEPEND=
> | simply because the depclean is broken for the cases you make.
>
> Not at all. The 'R' in RDEPEND means 'needed after the compile is
> done'. However, for the sake of keeping the tree small, naming the
> variable STUFFTHATISNEEDEDAFTERTHECOMPILEISDONEDEPEND is clearly
> impractical.

I agree here. If you don't want packages to be pulled in because of header 
files, you need support for that (perhaps in the form of subpackages, or 
a useflag). But IF the header files of a package are installed one should 
be able to assume that they keep on working. Even after buildtime-only 
dependencies have been removed.

In the case of embedded it is clear that what in binary distributions is 
part of the development package (.la files, static libraries, header 
files) is not desired at all. To break dependencies to only strip away 
some of the headers seems to me a half solution that breaks a lot and 
doesn't solve the problem either.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2005-10-26  9:00 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 [this message]
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=200510261058.22810.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