Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-doc
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-doc@g.o
From: Duncan <1i5t5.duncan@...>
Subject: Re: Portage per-package environment/behavior
Date: Sun, 1 Jan 2012 09:30:57 +0000 (UTC)
Joshua Saddler posted on Sat, 31 Dec 2011 19:13:59 -0800 as excerpted:

> 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.

You are correct that it used to be that way, but isn't that what emerge
--info <pkg>  was designed to fix and why portage's error messages are  
far more specific now about both that and various log files that should 
be posted than they used to be?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



References:
Portage per-package environment/behavior
-- Sven Vermeulen
Re: Portage per-package environment/behavior
-- Joshua Saddler
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Portage per-package environment/behavior
Next by thread:
Updated date in handbook
Previous by date:
Re: Portage per-package environment/behavior
Next by date:
Re: Portage per-package environment/behavior


Updated Apr 08, 2012

Summary: Archive of the gentoo-doc mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.