public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] DEPENDing on system components
Date: Tue Jul 24 14:43:01 2001	[thread overview]
Message-ID: <20010724144228.E25417@cvs.gentoo.org> (raw)
In-Reply-To: <3B5DC2ED.E9E2FEE1@gentoo.org>; from AGottinger@t-online.de on Tue, Jul 24, 2001 at 08:48:13PM +0200

On Tue, Jul 24, 2001 at 08:48:13PM +0200, Achim Gottinger wrote:

> Well the glibc dependencie is there to spearate packages that need glibc from
> those who do not link against it like for example docs or some java binary
> packages. If a package links agains flex then flex should be in the depend
> variable, if it only uses the flex binary during build, you don't have to add
> it to depend.

Well, I'd say that *technically*, you *can* refrain from adding it to DEPEND,
but it's still best to include it.  But technically, Achim is correct.  You
should only need to include flex or gcc in DEPEND if you need to ensure that
you are using a recent version of flex or gcc for building (which may be needed
if, for example, a particular ebuild simply won't compile with a previous
version of flex or gcc.)  Besides that, don't worry about adding standard
development stuff to DEPEND.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			



      reply	other threads:[~2001-07-24 20:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-23 12:25 [gentoo-dev] DEPENDing on system components Dan Armak
2001-07-23 12:30 ` Daniel Robbins
2001-07-23 12:49   ` Dan Armak
2001-07-23 12:51     ` Daniel Robbins
2001-07-23 13:36       ` Dan Armak
2001-07-24 14:07 ` Achim Gottinger
2001-07-24 14:43   ` Daniel Robbins [this message]

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=20010724144228.E25417@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@cvs.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