public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Dying on some CFLAGS instead of filtering them.
Date: Mon, 10 Jul 2006 06:16:00 -0400	[thread overview]
Message-ID: <1152526560.22145.5.camel@localhost> (raw)
In-Reply-To: <7573e9640607100134tf62c26awf5784b22fac348d5@mail.gmail.com>

On Mon, 2006-07-10 at 01:34 -0700, Richard Fish wrote:
> On 7/9/06, Denis Dupeyron <calchan@gentoo.org> wrote:
> > 2) If yes, are there any other flags that ebuilds should die on ?
> 
> My (user) opinion is that ebuilds should not die on CFLAGS, at least
> not until per-package CFLAGS are implemented.

per pkg cflags are here already it would fall under the per 
pkg env variables.


-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-07-10 10:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09 21:24 [gentoo-dev] Dying on some CFLAGS instead of filtering them Denis Dupeyron
2006-07-09 21:32 ` Ciaran McCreesh
2006-07-15 11:54   ` Denis Dupeyron
2006-07-15 13:59     ` Ciaran McCreesh
2006-07-09 23:51 ` [gentoo-dev] " Ryan Hill
2006-07-10 12:51   ` Denis Dupeyron
2006-07-11  2:32     ` Ryan Hill
2006-07-15 12:39       ` Denis Dupeyron
2006-07-15 16:33         ` Ryan Hill
2006-07-15 17:38           ` Ryan Hill
2006-07-16 19:55       ` Paul de Vrieze
2006-07-16 20:20         ` Ryan Hill
2006-07-16 19:37   ` Paul de Vrieze
2006-07-10  8:34 ` [gentoo-dev] " Richard Fish
2006-07-10 10:16   ` Ned Ludd [this message]
2006-07-10 16:01     ` Richard Fish
2006-07-10 17:08       ` Zac Medico
2006-07-10 20:30         ` Richard Fish
2006-07-10 20:42           ` Simon Stelling
2006-07-10 21:01             ` Richard Fish
2006-07-10 21:22           ` Donnie Berkholz
2006-07-10 12:25 ` [gentoo-dev] " Duncan
2006-07-10 13:20 ` [gentoo-dev] " Patrick McLean
2006-07-16 20:08   ` Paul de Vrieze
2006-07-10 14:42 ` Ciaran McCreesh

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=1152526560.22145.5.camel@localhost \
    --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