| 1 |
On 12 Nov 2015 21:07, Tim Harder wrote: |
| 2 |
> On 2015-11-11 14:42, Zac Medico wrote: |
| 3 |
> > Please unset all new internal function inside bin/save-ebuild-env.sh. |
| 4 |
> > Note that it already uses this line to unset functions beginning with |
| 5 |
> > ___eapi: |
| 6 |
> > |
| 7 |
> > unset -f $(compgen -A function ___eapi_) |
| 8 |
> > |
| 9 |
> > However, your __eapi functions will not be matched because they only |
| 10 |
> > begin with 2 underscores. |
| 11 |
> |
| 12 |
> Just to note another approach, pkgcore generates global and per-eapi |
| 13 |
> function lists at install time (or uses the generation scripts when |
| 14 |
> running from a checkout) so manually tracking lists of functions isn't |
| 15 |
> required. |
| 16 |
> |
| 17 |
> The main reason I set that up was because I sometimes forgot to add |
| 18 |
> functions to a similar list that was previously used. :) |
| 19 |
> |
| 20 |
> I'm not overly familiar with portage's bash code so I'm not sure if |
| 21 |
> that's feasible with its current structure. |
| 22 |
|
| 23 |
i was thinking of building lists too, but i'm not entirely sure how to |
| 24 |
tease that out of portage. |
| 25 |
-mike |
Archives