| 1 |
On Friday, September 21, 2018 3:59:26 PM PDT Chí-Thanh Christopher Nguyễn |
| 2 |
wrote: |
| 3 |
> Alexander Tsoy schrieb: |
| 4 |
> >> + sign_binary_path="${KV_OUT_DIR}/scripts/sign-file" |
| 5 |
> > |
| 6 |
> > Yet another way to screw up modules building. It relies on some binary |
| 7 |
> > in the kernel build dir that may break after openssl update (e.g. |
| 8 |
> > soname change). |
| 9 |
> |
| 10 |
> Maybe the sign-file application could be packaged, for example as part of |
| 11 |
> sys-apps/linux-misc-apps. |
| 12 |
> |
| 13 |
> |
| 14 |
> Best regards, |
| 15 |
> Chí-Thanh Christopher Nguyễn |
| 16 |
|
| 17 |
linux-mod.eclass already relies on full kernel build dir to be available to |
| 18 |
build modules. |
| 19 |
|
| 20 |
and depending on another ebuild means that it has to be keyworded on different |
| 21 |
arches to actually support signing on those arches. |
| 22 |
|
| 23 |
simple kbuild approach is better IMO, if a system can build a kernel and |
| 24 |
modules means it can sign it. |
| 25 |
Maintaining separate package, especially with kernel update pace will be a |
| 26 |
nightmare. |
| 27 |
|
| 28 |
-- |
| 29 |
Regads, |
| 30 |
Georgy Yakovlev |
| 31 |
Gentoo Linux Developer |
Archives