Hi, Sven Luther writes:
> Please tell me exactly in how far you feel that this would be so > much of a hindrance compared to the benefit of having kernel-image > installation work out of the box on non-pmac subarches ? mkvmlinuz serves the purpose of making some systems bootable given an uncompressed kernel and optionally an initrd. For other systems, the packages yaboot and quik serve the same purpose. Yet other systems use programs that are not packaged at all, such as BootX or a diskless setup or whatever. While you seem to care mostly for your Pegasos board, I want PowerPC kernel-image packages that work equally well on all subarchs. Following your logic, the way to achieve this would be to automatically pull in all packages mentioned above and let the postinst pick and configure the correct one. This has bloat written all over it, and is unacceptable. So I am suggesting to let the installation system and the user take care of a reasonable setup. If you think the postinst should fail on CHRP if it doesn't detect one, fine with me. Go implement it. > If you would have told me that the real problem is that mkvmlinuz pulls > in binutils, which is 6.6Mo or something such, then that would be a real > argument It's not an argument at all. Have you forgotten that one could do without binutils and create very small wrapper scripts if size was an issue? > Well, you were the one proposing to use the postinst_hook, where you not ? As a workaround, pending a real solution in kernel-package. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
