Bug 205220 - File conflicts
Summary: File conflicts
Status: CLOSED DUPLICATE of bug 192708
Alias: None
Product: Fedora
Classification: Fedora
Component: libgssapi
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Steve Dickson
QA Contact:
Depends On:
Blocks: multilibdevel
TreeView+ depends on / blocked
Reported: 2006-09-05 14:25 UTC by Bill Nottingham
Modified: 2014-03-17 03:02 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-10-02 21:53:53 UTC

Attachments (Terms of Use)

Description Bill Nottingham 2006-09-05 14:25:07 UTC
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

Comment 1 Steve Dickson 2006-09-05 15:05:08 UTC
How there be an file confliction with in itsself?

Comment 2 Bill Nottingham 2006-09-05 15:06:47 UTC
The headers conflict on i386 and x86_64.

Comment 3 Steve Dickson 2006-09-05 15:24:51 UTC
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...

Comment 4 Bill Nottingham 2006-09-05 15:29:33 UTC
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?

Comment 5 Steve Dickson 2006-09-05 15:50:25 UTC
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?

Comment 6 Bill Nottingham 2006-09-05 15:57:46 UTC
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).

Comment 7 Jeremy Katz 2006-10-02 21:53:53 UTC

*** This bug has been marked as a duplicate of 192708 ***

Note You need to log in before you can comment on or make changes to this bug.