| 1 |
On 03/22/2016 09:34 PM, Jonathan Callen wrote: |
| 2 |
> |
| 3 |
> For future reference, this would be a bit more efficient: |
| 4 |
> |
| 5 |
> grep -r -l --include="*.ebuild" "EAPI=6" . |
| 6 |
> |
| 7 |
> This way, grep only looks at the files you want to search anyway. |
| 8 |
> |
| 9 |
|
| 10 |
There's a chicken-and-egg problem with storing the EAPI in a variable |
| 11 |
within the ebuild whose EAPI you need to know to parse the ebuild that |
| 12 |
contains the EAPI variable whose value you need before you can parse the |
| 13 |
ebuild... |
| 14 |
|
| 15 |
It's a little silly, but the simplest workaround for that was to make |
| 16 |
the EAPI variable grepable. As a result, the actual regular expression |
| 17 |
that an EAPI declaration must match is in the PMS: |
| 18 |
|
| 19 |
https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-690007.3.1 |
Archives