files in both kdepimlibs4 and gpgme

[Jonathan Stickel]

Here is the relevant ticket:

https://trac.macports.org/ticket/52342


On 9/26/16 13:00 , macports-users-request at lists.macosforge.org wrote:
> Date: Sun, 25 Sep 2016 20:14:18 -0400 From: "Richard L. Hamilton"
> <rlhamil at smart.net> To: David Evans <devans at macports.org> Cc:
> macports-users list <macports-users at lists.macosforge.org> Subject:
> Re: files in both kdepimlibs4 and gpgme Message-ID:
> <03C214DE-6D8C-49B6-9A4E-DB3C8D9D0CDF at smart.net> Content-Type:
> text/plain; charset=windows-1252
>>> On Sep 23, 2016, at 21:56, David Evans <devans at macports.org>
>>> wrote:
>>>
>>> On 9/23/16 4:25 PM, Richard L. Hamilton wrote:
>>>>> The following files seem to be part of both ports, which
>>>>> seems to require a forced activate, i.e. seems to be
>>>>> something that ideally shouldn't happen; yet they're not
>>>>> listed as incompatible/conflicting, to the contrary, gpgme is
>>>>> listed as a library dependency of kdepimlibs4.
>>>>>
>>>>> Seems like something needs to be fixed about one or the
>>>>> other.
>>>>>
>>>>> Pending that, which should be forced in place last, if
>>>>> they're not identical? :-)
>>>>>
>>>>> _______________________________________________
>>>>> macports-users mailing list
>>>>> macports-users at lists.macosforge.org
>>>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>>>>>
>>>
>>> OK, which files?  Concerning gpgme, which was just updated, see
>>> https://trac.macports.org/ticket/52341.  Not sure if this is
>>> related or not.
>>>
>
> I do have the latest of both installed, that's when I ran into the
> problem.
>