| 1 |
...snip |
| 2 |
> |
| 3 |
> > In that case, I think the only viable way to make this work is to |
| 4 |
> > disable automatic stripping and handle stripping via custom code in |
| 5 |
> > the ebuild/eclass. |
| 6 |
> > |
| 7 |
> might work indeed if we do something like (pseudo-bash) |
| 8 |
> |
| 9 |
> if [[ module_sign == yes ]]; then |
| 10 |
> dostrip -x /lib/modules # to stop portage stripping .ko objects |
| 11 |
> manual-strip-respecting-features-nostrip -r /lib/modules |
| 12 |
> sign-all-modules -r /lib/modules |
| 13 |
> fi |
| 14 |
> [[ compress_modules == yes ]] && compress-modules -r /lib/modules |
| 15 |
> |
| 16 |
> |
| 17 |
> this will equire eapi-bumping couple of packages |
| 18 |
> https://qa-reports.gentoo.org/output/eapi-per-eclass/linux-mod.eclass/6.txt |
| 19 |
> and restricting linux-mod.eclass to eapi7 or later. |
| 20 |
> |
| 21 |
> |
| 22 |
> |
| 23 |
started playing with my old code and got blocked right away: |
| 24 |
|
| 25 |
looks like dostrip just creates a list of files/directories to strip |
| 26 |
and processed at the very end of install phase. |
| 27 |
|
| 28 |
so skipping strip and doing manual one might be problematic. |
| 29 |
internally portage uses estrip |
| 30 |
https://github.com/gentoo/portage/blob/master/bin/estrip |
| 31 |
which contains quite a lot of logic and code and I don't think |
| 32 |
partially re-implementing this in eclass code is appropriate. |
Archives