#52479: gpgme: install headers in a private location to avoid conflict and/or header confusion --------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch Port: gpgme | --------------------------+-------------------------------- Comment (by rjvbertin@…): Replying to [comment:1 larryv@…]:
Why should gpgme move anything? kdepimlibs4 is the one installing its own private stuff.
And why would kdepim4 have to be broken because another port suddenly starts installing files with the same name at the same location? If anything, kdepimlibs4 was installing those headers long before port:gpgme did, and if you read correctly the fix involves BOTH ports moving them. That's a direct consequence of how compiler include paths work: it's simply not feasible to instruct the compiler to ignore include/gpgme++ when looking for <gpgme++/foo.h>. We should think of this as 2 ports installing different implementations of a same idea which sadly can clash. Either both ports cannot be allowed to install the C++ wrappers, or both must make some changes - changes which in both cases are foreseen by the buildsystem. -- Ticket URL: <https://trac.macports.org/ticket/52479#comment:3> MacPorts <https://www.macports.org/> Ports system for the Mac operating system