[Fedora-packaging] *.h files in a directory under %{_libdir}?

[Richard W.M. Jones]

On Wed, Nov 12, 2008 at 01:36:52PM +0100, Mary Ellen Foster wrote:
> What is the best way to respond to this? I assume it's not encouraged
> to put *.h files into %{_libdir}, but on the other hand, breaking
> upstream assumptions like this isn't great either. PLBASE is
> documented as "the home directory of SWI-Prolog", but I'm not sure if
> it's actually guaranteed anywhere that .h files will be in this
> directory.

It's funny this should come up because I noticed that some glib & gtk
packages do this (when packaging for MinGW).  eg:

  $ find /usr/i686-pc-mingw32/sys-root/mingw/lib/ -name '*.h'
  /usr/i686-pc-mingw32/sys-root/mingw/lib/sigc++-2.0/include/sigc++config.h
  /usr/i686-pc-mingw32/sys-root/mingw/lib/glib-2.0/include/glibconfig.h
  /usr/i686-pc-mingw32/sys-root/mingw/lib/gdkmm-2.4/include/gdkmmconfig.h
  /usr/i686-pc-mingw32/sys-root/mingw/lib/glibmm-2.4/include/glibmmconfig.h
  /usr/i686-pc-mingw32/sys-root/mingw/lib/gtkmm-2.4/include/gtkmmconfig.h
  /usr/i686-pc-mingw32/sys-root/mingw/lib/gtk-2.0/include/gdkconfig.h
  /usr/i686-pc-mingw32/sys-root/mingw/lib/giomm-2.4/include/giommconfig.h

I left it as the upstream package was for now, but I'm sure this will
come up during review.  No idea what the right thing to do is or why
those packages put header files in such a weird place ...

Rich.

-- 
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top