public inbox for gentoo-doc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Saddler <nightmorph@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Portage per-package environment/behavior
Date: Mon, 2 Jan 2012 10:54:20 -0800	[thread overview]
Message-ID: <20120102105420.68c0d33a@angelstorm> (raw)
In-Reply-To: <20120101085925.GB1928@gentoo.org>

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

On Sun, 1 Jan 2012 08:59:25 +0000
Sven Vermeulen <swift@gentoo.org> wrote:

> On Sat, Dec 31, 2011 at 07:13:59PM -0800, Joshua Saddler wrote:
> > per-package cflags has never been an officially supported portage
> > feature. in fact, it's mostly been an env hack that users have
> > been actively discouraged from using. they can expect to see bugs
> > closed RESO WONTFIX when per-package cflag monkeying has been
> > detected. as such, we shouldn't be documenting how to do it.
> 
> I disagree. It is actively being suggested on #gentoo, and we
> already document features that could (or even will) result in
> RESO:WONTFIX, like using ~arch (both for a small set of packages as
> well as the entire system).

and who's suggesting it on #gentoo? users? devs? we need to talk to
the portage team and anyone else that would have to troubleshoot
build fixes caused by (ab)using it. if we get the okay from them,
then something like your proposed text should be added to the
handbook.

> I would rather have a <warn> in place then that sais it will hinder
> support during bug reports and might result in RESO:WONTFIX unless
> the user removes the specific settings and rebuilds with the system
> ones.

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

  reply	other threads:[~2012-01-02 18:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 10:14 [gentoo-doc] Portage per-package environment/behavior Sven Vermeulen
2011-12-28 17:20 ` wireless
2011-12-28 17:47 ` [gentoo-doc] " Duncan
2011-12-28 19:10   ` Sven Vermeulen
2011-12-28 18:01 ` [gentoo-doc] " Matthew Summers
2011-12-29 18:18 ` Sven Vermeulen
2011-12-30  1:56   ` [gentoo-doc] " Duncan
2011-12-30 12:29     ` Sven Vermeulen
2011-12-31 20:16   ` [gentoo-doc] " Sven Vermeulen
2011-12-31 23:41     ` [gentoo-doc] " Duncan
2012-01-01  3:13 ` [gentoo-doc] " Joshua Saddler
2012-01-01  8:59   ` Sven Vermeulen
2012-01-02 18:54     ` Joshua Saddler [this message]
2012-01-03 17:33       ` Sven Vermeulen
2012-01-01  9:30   ` [gentoo-doc] " Duncan

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=20120102105420.68c0d33a@angelstorm \
    --to=nightmorph@gentoo.org \
    --cc=gentoo-doc@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