[gentoo-user] Re: Anyone ever emerged dev-libs/boost with FEATURES="test" and finished?

[Harry Putnam]

Neil Bothwick <neil@××××××××××.uk> writes:

> On Tue, 06 Apr 2010 11:17:14 -0500, Harry Putnam wrote:
>
>> > You can set features on a per-package basis by putting FEATURES="blah"
>> > into /etc/portage/env/category/package.
>>
>> If that would also work for something like always using a specific
>> EXTRA_ECONF for a certain package:
>>
>>   EXTRA_ECONF="--enable-rootcommit"  <for the cvs package>
>
> It would.
>
>> Can you show an example of the necessary syntax?
>
> Just put the variable assignment in the file, it is sourced by bash when
> the ebuild is parsed, so most things that can go in an ebuild can go
> here. Usually it is used to override settings or set EXTRA_ECONF but you
> can use it to redefine the ebuild functions. Some people put a custom
> src_unpack() in here when they want to apply a patch, rather than
> putting a modified ebuild in an overlay.

Ahh very helpful, thank you.  Especially about putting custom
src_unpack stuff.  Fussing with creating a new ebuild is a pain to us
non devel types.

But one thing is unclear.  You say: 
`Just put the variable assignment in the file'

You don't mean without reference to a specific package do you.
Like:
  cat /etc/portage/env/category/package
  EXTRA_ECONF="--enable-rootcommit"

So is it:
  cat /etc/portage/env/category/package
  dev-util/cvs  EXTRA_ECONF="--enable-rootcommit"

Or something else?