James Carlson wrote: > Garrett D'Amore writes: >> One of the things that I think we (Sun) do poorly is expose header files >> (and structures) that have no business being in /usr/include. For >> example, device-driver private headers that only are used by the driver >> itself have no business being exported in /usr/include. (Most NIC >> drivers, for example, fall into this category. I suspect this is true >> for many other target/leaf drivers as well.) > > Historically, we've published kernel- and driver-related header files > unless there's a specific reason _not_ to publish. They're not > classed as documentation, but they're also not "secrets," so the fact > that they're generally private isn't that much of an issue. > > Except perhaps for folks who mistakenly think that header files _are_ > documentation. Some files have appropriate warnings, but in general, > there's not much we can do about that. There are all sorts of > inappropriate things one can use as "documentation" (other than actual > documentation) if one were so inclined. > > Yes, it's sometimes confusing and wasteful to install headers that > nobody can actually use. See CR 4696464. > > (The comments field on that CR should mostly be moved to > "description," but you'll need meem's and Darren's permission.)
Permission granted for my comments in that CR. -- Darren J Moffat _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
