public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: Gentoo Developers <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] per package cflags (was Re: Do we want optimal performance?)
Date: Wed, 08 Sep 2004 19:26:43 -0700	[thread overview]
Message-ID: <20040909022643.GE6455@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <413FB713.3030404@gentoo.org>

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

On Wed, Sep 08, 2004 at 09:51:15PM -0400, Travis Tilley wrote:
> Daniel Goller wrote:
> >although i am against overly tweaking CFLAGS, someone suggested 
> >something that might be more sane to ask for:
> >
> >/etc/portage/packages.cflags
> >
> >an easy way to maintain your cflags you worked so hard for to obtain, 
> >you can trade them in the forums or ebay and then append to your file, 
> >not much work to implement in my eyes, and all the testing work is done 
> >by those who want it
> mkdir /etc/portage and copy this file there (MUCH thanks to solar for 
> writing this. he like... kicks ass an stuff). it implements an 
> /etc/portage/package.cflags without needing to patch portage. i think 
> this might require portage 2.0.51_pre... no idea, i havent used 2.0.50 
> in a while.
[snip]
Could this be generalized to do /etc/portage/package.env like somebody
else asked for?

And then simply put a CFLAGS line in the file referenced by package.env,
as it seems that it really would belong there.

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

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

  reply	other threads:[~2004-09-09  2:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 10:15 [gentoo-dev] Do we want optimal performance? Klavs Klavsen
2004-09-08 11:29 ` Paul de Vrieze
2004-09-08 12:03   ` Corvus Corax
2004-09-08 13:16     ` Paul de Vrieze
2004-09-08 12:19 ` Alin Nastac
2004-09-08 13:24   ` Marcus D. Hanwell
2004-09-08 13:43     ` Patrick Lauer
2004-09-08 14:21     ` Klavs Klavsen
2004-09-09  7:52       ` Paul de Vrieze
2004-09-08 12:49 ` Spider
2004-09-08 17:16   ` Robert Moss
2004-09-08 18:20 ` Chris Gianelloni
2004-09-08 19:11   ` Klavs Klavsen
2004-09-08 19:54     ` Paul de Vrieze
2004-09-08 20:05     ` Marcus D. Hanwell
2004-09-08 19:41 ` Lisa Seelye
2004-09-09  0:49 ` Daniel Goller
2004-09-09  1:51   ` [gentoo-dev] per package cflags (was Re: Do we want optimal performance?) Travis Tilley
2004-09-09  2:26     ` Robin H. Johnson [this message]
2004-09-09  3:42       ` Ned Ludd
2004-09-09  3:49         ` Robin H. Johnson
2004-09-09 17:23           ` Robert Moss
2004-09-09  4:41         ` Will Buckner
2004-09-09  4:51           ` Ciaran McCreesh
2004-09-09  6:07   ` [gentoo-dev] Do we want optimal performance? Klavs Klavsen

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=20040909022643.GE6455@curie-int.orbis-terrarum.net \
    --to=robbat2@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