Bug 205220
| Summary: | File conflicts | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill Nottingham <notting> |
| Component: | libgssapi | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-10-02 21:53:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 192658 | ||
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). |
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