| 1 |
On Wed, 17 Sep 2014 03:40:37 +0000 (UTC), James wrote: |
| 2 |
|
| 3 |
> > You can often do it without touching the ebuild at all by putting |
| 4 |
> |
| 5 |
> > post_src_unpack() { |
| 6 |
> > cd "${S}" |
| 7 |
> > epatch_user |
| 8 |
> > } |
| 9 |
> |
| 10 |
> > in /etc/portage/env/category/package[-version] |
| 11 |
> |
| 12 |
> Nice trick to know. But, |
| 13 |
> I do not have an /etc/portage/env/ dir? |
| 14 |
> Just make them up? |
| 15 |
|
| 16 |
Yes. Portage doesn't know which directories you need, just create them |
| 17 |
when you do. |
| 18 |
|
| 19 |
> Or is this the reference: |
| 20 |
> http://wiki.gentoo.org/wiki//etc/portage/env |
| 21 |
|
| 22 |
That's a different, but equally useful, use of /etc/portage/env. |
| 23 |
|
| 24 |
> Any docs somewhere as this looks more like a "sets" trick? |
| 25 |
|
| 26 |
The functions are explained in man 5 ebuild, /etc/portage is covered in |
| 27 |
man portage. The rest was gathered by starting at http:///www and working |
| 28 |
down... |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Neil Bothwick |
| 33 |
|
| 34 |
"If Micro built cars, the worlds population would be in decline" |
Archives