<div dir="ltr"><div>Hi Stefan</div><div><br></div><div>Thanks for the list :) <br></div><div>we will fix that shortly <br></div><div><br></div><div>Most of the conflicts handling in the kde ports is done by dumb magic <br></div><div>(for example a "CATEGORY=kde-applications" port "foo" will conflict with <br></div><div>"foo-kde4" if it's "kde:5" based and with "foo" if its "kde:4" -- thats why <br></div><div>"akonadi" already properly conflicts with "akonadi-kde4" but not the <br></div><div>other way around -- theoretically at least, if there wasn't an error :P).</div><div><br></div><div><br></div><div>mfg Tobias<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 25 May 2018 at 23:18, Stefan Esser <span dir="ltr"><<a href="mailto:se@freebsd.org" target="_blank">se@freebsd.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 25.05.18 um 13:08 schrieb Adriaan de Groot:<br>
<div><div class="h5">> On Thursday, 24 May 2018 22:45:20 CEST Stefan Esser wrote:<br>
>> PS: Do you want me to open a PR for such issues? Since I'm currently<br>
>> testing the re-implementation of portmaster I'm working on, it is<br>
>> highly probable that there will be more such problems found (which<br>
>> I need to diagnose to see whether it is a bug in portmaster or an<br>
>> omission in the port).<br>
> <br>
> I'm going to say "no, we don't need a PR for that", just drop the list a note, <br>
> and/or prod us on #kde-freebsd on FreeNode, just in case.<br>
> <br>
> [ade] (with kde@ hat on)<br>
<br>
</div></div>Hi Adrian,<br>
<br>
thank you your reply and the patch in D15571.<br>
<br>
I've spent some time today on an effort to identify all affected ports, and<br>
the result is the following list:<br>
<br>
databases/akonadi-kde4 databases/akonadi<br>
<br>
deskutils/kdepimlibs-kde4 databases/akonadi<br>
<br>
net/akonadi-mime deskutils/kdepimlibs-kde4<br>
<br>
net/kmailtransport deskutils/kdepimlibs-kde4<br>
<br>
sysutils/plasma5-ksysguard sysutils/ksysguardd-kde4<br>
<br>
sysutils/polkit-kde sysutils/plasma5-polkit-kde-<wbr>agent-1<br>
<br>
x11/kde-workspace-kde4 devel/plasma5-khotkeys<br>
x11/kde-workspace-kde4 sysutils/plasma5-kinfocenter<br>
x11/kde-workspace-kde4 sysutils/plasma5-kmenuedit<br>
x11/kde-workspace-kde4 sysutils/plasma5-ksysguard<br>
x11/kde-workspace-kde4 sysutils/plasma5-libksysguard<br>
x11/kde-workspace-kde4 sysutils/plasma5-<wbr>systemsettings<br>
x11/kde-workspace-kde4 x11-wm/plasma5-kwin<br>
<br>
x11/plasma5-kactivitymanagerd x11/kactivitymanagerd<br>
<br>
x11/plasma5-plasma-desktop x11/kde-runtime-kde4<br>
x11/plasma5-plasma-desktop x11/kde-workspace-kde4<br>
<br>
x11/plasma5-plasma-workspace x11/kde-workspace-kde4<br>
<br>
Each port in the 1st column contains files also present in the port in the 2nd<br>
column, but lacks a CONFLICTS_INSTALL entry. E.g. in the case of akonadi it<br>
appears, that the KF5 port is marked as conflicting, but the KDE4 port lacks<br>
that conflicts annotation. (I.e., the ports in column 1 need to be marked as<br>
conflicting with the ports in column 2.)<br>
<br>
I have generated this list by fetching all KDE4 and KF5 packages and matching<br>
all the files they contain against each other, then identified the ports that<br>
correspond to those packages and finally checked for an CONCLICTS entry.<br>
<br>
I have kept some of the intermediate results and could try to repeat the match<br>
steps in case I made a mistake and the results are not correct (I have not<br>
verified each of those combinations, but the samples I checked were correctly<br>
identified).<br>
<br>
Seems that most of the conflicts have already been correctly registered, since<br>
the list of conflicting pairs was about an order of magnitude longer before I<br>
had filtered out all the pairs that were already correctly annotated.<br>
<br>
Best regards, STefan<br>
<br>
</blockquote></div><br></div>