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

[Neil Bothwick]

On Tue, 06 Apr 2010 15:17:27 -0500, Harry Putnam wrote:

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

I find copying the existing ebuild to an overlay and adding one epatch
line a lot easier than writing a custom src_unpack() function.

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

Yes I do.

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

No, it is

$ cat /etc/portage/env/dev-util/cvs
EXTRA_ECONF="--enable-rootcommit"


-- 
Neil Bothwick

"We demand rigidly defined areas of doubt and uncertainty!"