> We now have a single library, and still many header files for various > sections of the API provided by that library. These are all named > "libdl<something>.h". Since there is no "libdl<something>" library and > all of these libdladm-related header files are in the top level of > /usr/include, I'm not enamored with the naming scheme. It would make > more sense to me to have a subdirectory named /usr/include/libdladm/, in > which we have header files such as <libdladm/aggr.h>, <libdladm/wlan.h>, > <libdladm/link.h>, etc... This isn't a very big deal since these are > consolidation private header files that we don't ship, but maybe I'd > consider this a more serious comment if/when the interfaces are promoted > and we start shipping these files in /usr/include. Note that there is > some precedent for shipping a library's bundle of header files under > /usr/include/<library-name>/
Hmm, I don't have a strong opinion on this, but as you say, none of these headers are even shipped at present so I don't see a strong reason to do this reorganization now. -- meem
