the src for linux-headers is now the upstream kernel archive file, which is fine to me, but it comes to a price: >>> Completed installing sys-kernel/linux-headers-5.2 into /var/tmp/portage/sys-kernel/linux-headers-5.2/image/ * Final size of build directory: 950328 KiB (928.0 MiB) * Final size of installed tree: 7048 KiB ( 6.8 MiB) while it's been a lot less with the repacked linux headers: >>> Completed installing sys-kernel/linux-headers-4.19 into /var/tmp/portage/sys-kernel/linux-headers-4.19/image/ * Final size of build directory: 69216 KiB (67.5 MiB) * Final size of installed tree: 6776 KiB ( 6.6 MiB) Reproducible: Always Steps to Reproduce: yes, this happens every time. it's ok to use that much of tmp space, but please check for it to be available. there are embedded devices still. Actual Results: install breaks if there's less than 1gb of temp space available nothing in addition to the above.
Did you observe actual failure? Or does it cause any other kind of problems? I'd like to see practical problem first. These are linux headers. Headers presence implies you have a compiler installed and plan to use it (which is itself a few hundreds megabytes), development libc headers (a few hundreds megabytes), distfiles space and more. 1GB is not much for a build host. Even in terms of RAM available. kernel-2.eclass is there for a long while and never had a check-reqs plumbed in.
Well, if you're relucant to add a check size function to the ebuild, for the sake of not wanting it to be too complex, that's fine by me. I'll just have to keep in mind to cross-compile the headers in the future. Or copy over the rootfs to an external hard disk drive and compile there, don't want to kill my sd card.
(In reply to tt_1 from comment #2) > Well, if you're relucant to add a check size function to the ebuild, for the > sake of not wanting it to be too complex, that's fine by me. I'll just have > to keep in mind to cross-compile the headers in the future. Or copy over the > rootfs to an external hard disk drive and compile there, don't want to kill > my sd card. It's still not clear from you setup what you are optimising for. If you plan to build anything on a target unpacking/copying linux sources around once will not be your worst problem.
