From: foser <foser@foser.dyn.warande.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE flags again (informix, memlimit)
Date: 14 May 2003 17:10:53 +0200 [thread overview]
Message-ID: <1052925052.12187.5.camel@rivendell> (raw)
In-Reply-To: <20030514160813.4866e0a7.spider@gentoo.org>
On Wed, 2003-05-14 at 16:08, Spider wrote:
> Icc adds extra dependencies, since the binary must be run with icc
> installed, since it links to icc libraries. so its both a compile time
> and a runtime dependency.
>
> jikes, I dont know about, neither about the haskell compiler choice
> flags.
Ofcourse they do have deps, but so does our standard compiler (we don't
have gcc listed in every ebuild). I do not question their existance, i
question their position in comparison to most other USE flags, compiling
options (how do you want to compile) vs. compile time options (what do
you want to compile exactly = USE). The suggested division is just a
superficial one.
- foser
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-14 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 9:14 [gentoo-dev] USE flags again (informix, memlimit) Robin H.Johnson
2003-05-14 13:47 ` foser
2003-05-14 14:08 ` Spider
2003-05-14 15:10 ` foser [this message]
2003-05-14 20:41 ` Robin H.Johnson
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=1052925052.12187.5.camel@rivendell \
--to=foser@foser.dyn.warande.net \
--cc=gentoo-dev@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