> > borsenkow> - merge current kernel-headers into glibc-devel. It belongs there > anyway > borsenkow> - split current kernel-source into kernel-headers and kernel- > source > borsenkow> proper > borsenkow> - deliver kernel-headers with specially prepared files allowing > you to > borsenkow> compile external modules for your currently running kernel (as it > is > borsenkow> now) > > problem is, grep for .h files outside of include/* and you will find > that external modules need that files :(, i.e. usb drivers out of the > kernel needs includes in drivers/usb, scsi drivers in drivers/scsi :( >
Are we speaking about the same thing? When I say "external modules" I mean - modules not included in kernel-source. Get any tarball off the net (nVidia, Aureal, whatever). Do you mean such drivers do include references to headers inside a kernel tree? Can you give an example? Even in this case it should still work BTW. You just have to install both headers and source to compile such module - but what this module needs .depend files for? > I wanted to do what you are suggesting here several times, but it is > not possible without breaking compilation of external modules still > more. > > Only thing that I can think of is ship also a .you_really_need to > run make mrproper, and add things to the main makefile for it running > make mrproper before *config _only_ the first time. > > What do you think? > Yes, I think it needs to be done. regards -andrej > borsenkow> - deliver kernel-source in make mrproper state. > > borsenkow> This has a number of advantages (in no particular order): > > borsenkow> - people are no more confused with kernel-headers versions (it is > borsenkow> confusing) > > Yes, kernel-headres should be included in glibc-devel, no objection to > that at all. > > borsenkow> - those who need only compile 100K kenel modules are not forced > to > borsenkow> install 100M worth of files. They need only kernel-headers. It > actually > borsenkow> coiuld even be installed by default (if development environment > has been > borsenkow> selected during installation) > > borsenkow> - those who wish to compile there kernel get virgine state and > know that > borsenkow> they must configure it first > > borsenkow> any takers? > > What do you think of my solution, it is simpler and I think that it > fixes the problem. Will do it for next kernel. > > Later, Juan. > > > -- > In theory, practice and theory are the same, but in practice they > are different -- Larry McVoy
