On 5 March 2017 at 00:59, Peter Humphrey <[email protected]> wrote: > > I just can't believe it. They're issuing a general-purpose tool, to work > everywhere, and they don't test it on a representative sample of systems?
It was tested, otherwise how could the conflict with kde-apps/gpgmepp and kde-apps/kdepimlibs:4 been known? Upstream has merge some external libraries into its own code base and provided an option to disable these exactly for this use case. Adding USE="-cxx -qt5" or masking this package provides remedy for those who still use kdepimlibs:4, both are standard gentoo procedures. As apposed to what you present in previous messages, a "standard kde" system may or may not include kdepimlibs:4. We delayed too much stabilization of gpgme to allow proper resolution, however, no reason to delay any more as no issue for these that do not use kdepimlibs:4 and for these who use a simple USE change or mask resolves the issue. > I just can't believe it. They're issuing a general-purpose tool, to work > everywhere, > and they don't test it on a representative sample of systems? Indeed, we provide general-proposed tool that with correct setup can work in most cases as supported as outlined by the designated upstreams, while bridging the gaps and permutations as much as we can. Regards, Alon
