Messages in this thread |  | | | Date | Sat, 20 Jun 1998 16:11:02 -0400 | | From | Danek Duvall <> | | Subject | Re: Header files and interfaces |
| |
In the specific case of ext2 tools, wouldn't it do to split e2fslibs from the e2fsprogs package? Any kernel headers could be appropriately munged and copied into the libs package, which would be installed as a prerequisite to compiling any of the tools.
That way, Linus doesn't have to worry about kernel headers, there's only one copy going on (and only one person who needs to worry about it), and it can change whenever it needs to, without waiting for the glibc people to do something that, admittedly, is specific to a very small sector of programs.
I can see that this wouldn't work in all cases ... if there's only one header in question, and there isn't really a body of library code that can be distributed as a package. But is it a workable solution for larger interfaces?
Danek
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
|  |