Hans de Graaff writes:
> wise me up as to policy, I bet there is a consistent pattern
here that
> we could take advantage of (and not just in Fedora).
Same thing with Gentoo. We also have the gdbm include files
in /usr/include/gdbm. We solve this by adding -I/usr/include/gdbm to the
CFLAGS when the user wants to build with gdbm.
How about other libraries in general? What I'm hoping for is a (more
or less, doesn't have to be perfect) consistent pattern where a
package named foo generally has includes in <foo/foo.h> and
<foo/bar.h>. Or is that too much to expect for non-pkgconfig
packages? (Ie, maybe by now all the packages following this pattern
also support "pkgconfig --includes foo", too?)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta