1 |
On 1/25/09, Grant <emailgrant@×××××.com> wrote: |
2 |
> I could have sworn there was a way to specify a patch to be applied to |
3 |
> an emerge from the command line, something like: |
4 |
> |
5 |
> EPATCH=file.patch emerge packagename |
6 |
> |
7 |
> I've been searching Google and the mailing list but I can't find |
8 |
> mention of it anywhere. Was it a figment of my imagination? |
9 |
|
10 |
This would be nice, but I don't think you can do this, at least not |
11 |
this way. You can grep for EPATCH_* under /usr/portage to see some |
12 |
samples of how EPATCH_* stuff seems to work, especially some php |
13 |
eclasses give nice examples on one line. |
14 |
|
15 |
Still, I think in practice it is for ebuilds' and eclasses' internal |
16 |
use only -- and even then only for ebuilds/eclasses which inherit the |
17 |
eutils.class which in turn implements epatch() which actually does |
18 |
anything with the values. |
19 |
|
20 |
Inside an ebuild you can set up those variables in the right spot |
21 |
(e.g., right in the middle of src_unpack() after unpacking the source) |
22 |
and immediately call epatch(). Coming from command line there probably |
23 |
won't be that dangling epatch() call waiting for your parameters in |
24 |
the right spot -- and other epatch calls or setting those variables |
25 |
within the ebuild may interfere or override the settings you provided |
26 |
depending on the case. |
27 |
|
28 |
Still, I'd be happy to be mistaken, this would make my life easier as well. |
29 |
|
30 |
-- |
31 |
Arttu V. |