Description of problem:
file /usr/include/gssglue/gssapi/gssapi.h from install of
libgssapi-devel-0.10-1 conflicts with file from package libgssapi-devel-0.10-1
How there be an file confliction with in itsself?
The headers conflict on i386 and x86_64.
So both version (i386 and x86_64) have to be able to
live on the same machine? If that's the case, there
will probably be problems with nfs-utils-lib as well...
Correct; the idea is that you can develop for both arches on x86_64. Why would
the -lib packge conflict - the libraries should be under different paths?
yes... the gssglue/gssapi/gssapi.h is where the
package config file (i.e. libgssapi.pc) defines
where the libgssapi header file live...
So as not to reinvent the wheel... How is this
handled in other packages and is there some
type of naming convention that should be used
to decipher between x86 and x86_64 paths?
Generally, pkg-config files go in $(libdir)/pkgconfig.
Arch-specific header files could be in /usr/include/<name>/<arch>, or in
$(libdir)/<name>/include (glibc does the former, glib the latter).
*** This bug has been marked as a duplicate of 192708 ***