| 1 |
On Tue, 06 Apr 2010 11:17:14 -0500, Harry Putnam wrote: |
| 2 |
|
| 3 |
> > You can set features on a per-package basis by putting FEATURES="blah" |
| 4 |
> > into /etc/portage/env/category/package. |
| 5 |
> |
| 6 |
> If that would also work for something like always using a specific |
| 7 |
> EXTRA_ECONF for a certain package: |
| 8 |
> |
| 9 |
> EXTRA_ECONF="--enable-rootcommit" <for the cvs package> |
| 10 |
|
| 11 |
It would. |
| 12 |
|
| 13 |
> Can you show an example of the necessary syntax? |
| 14 |
|
| 15 |
Just put the variable assignment in the file, it is sourced by bash when |
| 16 |
the ebuild is parsed, so most things that can go in an ebuild can go |
| 17 |
here. Usually it is used to override settings or set EXTRA_ECONF but you |
| 18 |
can use it to redefine the ebuild functions. Some people put a custom |
| 19 |
src_unpack() in here when they want to apply a patch, rather than |
| 20 |
putting a modified ebuild in an overlay. |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Neil Bothwick |
| 25 |
|
| 26 |
Picard: 'What do the sensors say Mr Data?' |
| 27 |
Data: 'They tell us that we can't say "F*ck" Sir." |
Archives