| 1 |
Am 05.07.2012 01:58, schrieb Rich Freeman: |
| 2 |
> About the only really "safe" approach would be to run as a limited |
| 3 |
> user, install it into some offset/chroot, package it, and then |
| 4 |
> install it using portage as a binpkg. That actually has advantages |
| 5 |
> on many levels, and it basically is what we do with everything else. |
| 6 |
|
| 7 |
I think that's a good idea to have a script which packs the needed files |
| 8 |
(kernel) and modules into a binpkg: |
| 9 |
- define KBUILD_OUTPUT |
| 10 |
- after emerging the sources (or downloading), configure and build your |
| 11 |
kernel |
| 12 |
- launch a script which 'installs' the modules and also the kernel in a |
| 13 |
sandbox like portage normally does and generates a binpkg with a given |
| 14 |
version number (or auto generated based on kernel version) |
| 15 |
- install the binpkg (or advise the script to do so) |
| 16 |
|
| 17 |
this has the advantage, we can build the kernel as user and also have |
| 18 |
all installed files recorded by the package manager (which is |
| 19 |
unfortunately not the case with the current approach) which makes |
| 20 |
removing them much easier (only remove -source- and/or -bin- pkg) |
| 21 |
|
| 22 |
/martin |
Archives