Re: forget *documenting* libiberty -- how about *installing* it?

[Russ Allbery <rra at stanford dot edu>]

Jeffrey A Law <law@redhat.com> writes:

> Either $(prefix)/include or $(prefix)/include/libiberty would make the
> most sense to me.

I'd like to cast a vote for $(prefix)/include/libiberty; once one has a
non-trivial number of libraries installed, collisions with any remotely
common name become a real possibility, and when there's more than just a
single header file with the same name as the library it's really a lot
neater to use a subdirectory.

This also has the advantage that:

    #include <libiberty/obstack.h>

is somewhat self-documenting with respect to where the functions being
used came from, whereas:

    #include <obstack.h>

makes one guess what library provides that functionality.  (This may be a
bad example, since obstack.h is a system header on GNU/Linux systems.)

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>