| Summary: | app-crypt/gpgme-1.5.5: incorrect location for header file | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | William Hubbs <williamh> |
| Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | alonbl |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
William Hubbs
2017-06-15 00:54:37 UTC
This actually applies to all versions of gpgme in the tree I think. I'll admit to not being fully sure about this, but my understanding is that if you have a single header file you install it directly in /usr/include but you make a subdirectory of /usr/include if you have multiple header files or if there is a conflict between the name of your header file and another one in /usr/include. gpgme had the nature of breaking its own api, it was slotted. not sure why you open issues on gpgme that is obsoleted. the gpgme-1.8 already fixes that while keeping backward compatibility for now. *** This bug has been marked as a duplicate of bug 458918 *** (In reply to Alon Bar-Lev from comment #2) > gpgme had the nature of breaking its own api, it was slotted. > not sure why you open issues on gpgme that is obsoleted. > the gpgme-1.8 already fixes that while keeping backward compatibility for > now. It turns out that I'm stuck on gpgme-1.5 because of #604902. |