Closed esben closed 7 years ago
We should probably try to make kernel-dev contain roughly what a distro's kernel-headers package contains, so certainly .o and .o.cmd do not belong there.
Ok, I updated with .o removal also.
Pet peeve: Could you please not spawn a process for every file to delete; replace -exec rm {} \;
by just -delete
. Other than that, ack.
Done.
I was not aware of -delete
, so I learned something today :)
Have just identified a project (ethercat-modules on powerpc) expecting the *.o files to be available. Or more precisely - I think the linker expects it. Also found this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355344
I don't believe there are any use of them in kernel-dev packages, and many of them hardcode path to the originating recipe workdir, which is obviously bad (with or without rmwork!).
Could/should we remove the .o files also? Do they serve a purpose in kernel-dev packages?
Signed-off-by: Esben Haabendal esben@haabendal.dk