> > are supposed to work for all architectures. This worked fine when > > ports meant Linux to -alpha, -i386, -mips, etc., but is not working > > out so well for us with our "hurd-i386" architecture. > > I don't see why one should want to use the package system to prevent > people from installing Linux kernel sources on the Hurd. It's > reasonable for someone to want to cross-compile them, isn't it? > That's a good point (although the hurd is still slower than an equivalent Linux setup, so cross compiling in hurd->linux direction seems humorous(: )
The main issue is that we don't want a naive user to install "kernel sources" and compile them, thinking he is getting an update to his system. Perhaps it's enough if they are all labeled properly, and the kernel build tools under Debian could refuse to install them in the /boot directory of a hurd system. -Brent
