[KDE/Mac] Upgrade to 4.13.3 in Macports

[Nicolas Pavillon]

Hello,
On 26/09/2014 13:59, Marko Käning wrote:
> Hi Nicolas, René and Ian,
>
> On 13 Sep 2014, at 10:50 , Nicolas Pavillon <nicos at macports.org> wrote:
>> - Review of all dependencies, in order to make several implicit ones now explicit
> yep, that’s important, as it showed itself with kstars and eigen3.
Well, this is slightly different. Implicit dependencies are the ones 
satisfied by ports below in the tree, which means that they would always 
be present. Making them explicit just makes things clearer for maintenance.
In the case of kstars, it is a plain and simple missing dependency. They 
upgraded from eigen2 to eigen3 and I forgot to change the dependency in 
the port.

> It’s always best to start installation at least from a clean machine.
> In principle one would have to work like the buildbot - i.e. always
> clean everything before installing any port - but this isn’t realistic
> considering the large number of KDE 4.13 ports.
This is still done when upgrading on the main tree, where all ports are 
passing through the bots. I usually upgrade by groups to follow if 
problems such as missing dependencies are happening during the commits.
>> There are then some patches that I would consider rather safe to include:
>> - Use of OSX keychain (https://git.reviewboard.kde.org/r/119838/) This seems like
>> a nice feature, with its use based on a variant, which would thus be mainly “on demand”.
> This doesn’t seem to be included yet, right? (TODO?)
It is included, you can check the variant "osxkeychain". Then, all the 
patches you are referring to below are included in the version I sent 
you. Normally, that includes all changes up to Sep. 23rd.
> P.P.S.: Nicolas, are you registered as a KDE developer? If not, please send me any
>          patches and I’ll include them in the repo for you (TODO).
I am not, but all the patches were contained in the distribution I sent 
you, so you they should readily be included.

Cheers,

Nicolas

>> In addition to these, there are then several patches, where I am not sure if they
>> should be included at once, or left out for now and included later.
>> - KCrash and Dr. Konqi (https://git.reviewboard.kde.org/r/119497/ and
>>    https://git.reviewboard.kde.org/r/119498/).
>>
>> There has been apparently quite some debate, and apparently, Ian, you are still
>> working on a more elaborate solution for this problem, right? Therefore, should
>> the present patches be used in the meantime, or are they not yet mature enough?
> I haven’t looked into these yet. (TODO)
>
>
>> - Native file dialogs (https://reviewboard.kde.org/r/119243/). This seems to be
>>    deeper changes, that I would tend to leave out for now in order to see how 4.13
>>    is going first.
> +1 (TODO: But we should add a variant for it for testing anyway.)
>
>
>> - System trays menus (​https://reviewboard.kde.org/r/120149/). Again, these would
>>    be changes I would leave out for now to test 4.13 first.
> +1 (TODO: But we should add a variant for it for testing anyway.)
>
>
>> There are also some proposed changes in kdepim4, but I did not look at them yet.
> Same for me up to now.
>
>
> I hope the branch ‘KDE4.13’ in our git will now a good basis to get a joint polishing
> (TODO) of all these ports done.
>
> Greets,
> Marko
>
>
> P.S.: René and Ian, you guys are added as developers to [1], so feel free to update
>        the repository regarding your patches (TODO).
>
> P.P.S.: Nicolas, are you registered as a KDE developer? If not, please send me any
>          patches and I’ll include them in the repo for you (TODO).
>
> _______________________________________________
> kde-mac at kde.org
> List Information: https://mail.kde.org/mailman/listinfo/kde-mac
> KDE/Mac Information: http://community.kde.org/Mac