[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-games-devel
Subject:    Re: [Kde-games-devel] Merge frameworks in master
From:       Ian Wadham <iandw.au () gmail ! com>
Date:       2015-01-02 9:06:27
Message-ID: 0D413C7B-A3B4-4226-9EF5-0B0AF4915713 () gmail ! com
[Download RAW message or body]


On 01/01/2015, at 7:48 PM, laurent Montel wrote:

> Le Thursday 01 January 2015 14:31:31 Ian Wadham a =E9crit :
>> Hi Laurent,
>> =

>> On 31/12/2014, at 5:23 PM, laurent Montel wrote:
>>> Le Wednesday 31 December 2014 15:02:50 Ian Wadham a =E9crit :
>>>> Thank you very much, Laurent, for all your work on this.  I particular=
ly
>>>> appreciate you tackling KGoldrunner and Palapeli, which are quite
>>>> large code-bases.
>>>> =

>>>> On 31/12/2014, at 9:54 AM, Albert Astals Cid wrote:
>>>>> El Dimarts, 30 de desembre de 2014, a les 20:59:44, laurent Montel va
>>>>> =

>>>>> What the maintainers of the others say?
>>>> =

>>>> I am still the maintainer of KGoldrunner, KJumpingCube, KSudoku, Kubri=
ck
>>>> and Palapeli.
>>>> =

>>>> Merging the Frameworks versions into master would make it impossible f=
or
>>>> me
>>>> to work on them in the foreseeable future.  The reason is that I work =
on
>>>> an
>>>> Apple MacBook using OS X operating system and nobody has yet succeeded=
 in
>>>> building and running Frameworks-based applications on that platform.
>>>> =

>>>> We have one guy (Marko K=E4ning) working on it, but he is on Christmas
>>>> holidays now.  He is using Bovo and KMahjongg as test cases.  Just bef=
ore
>>>> Christmas he reported that he had KMahjongg running, but it would not
>>>> Quit
>>>> properly=85
>>> =

>>> Ok but I can't help you in macosx support.
>> =

>> We do not expect you to, Laurent=85 :-)
>> =

>>>> So please, please hold your horses for now, Laurent=85 :-)  Please do =
not
>>>> merge the frameworks branch into master.
>>> =

>>> Ah.
>>> So you don't think it=94s a good idea to move theses applications to ne=
xt
>>> kf5
>>> release ?
>> =

>> I don't understand what it is that you would like to do.  In your origin=
al
>> email you said:
>> =

>>    "Now I would like to merge in master as I think it's a good idea to h=
ave
>> it in next kde release 'kde-15.3=84 kde-15.4=84 I don't know when it will
>> release.
>> =

>>     What do you think about it ?"
>> =

>> As far as I am aware, and I think I heard this from Albert on another li=
st,
>> there will be no further releases from master --- KDE 4.14 was the last
>> one.  Indeed, if I understand correctly, the concept of "master" is
>> obsolete in Frameworks/KF5 and releases are done from parallel
>> repositories, e.g. Dr Konqi source code exists in the kde/kde-runtime
>> repository and also (temporarily, I am told) in plasma-workspace reposit=
ory
>> on KF5.
>> =

>> I am worried by what you meant by "merge in master" in the above.  If you
>> meant frameworks+master -> master, I am against that, because I am using
>> kdesrc-build to get code for the latest KDE 4 and cannot (yet) compile a=
nd
>> use KF5 code on Apple OS X.  OTOH, if you meant frameworks+master ->
>> frameworks, that is OK by me.  It will leave me shooting at a fixed targ=
et
>> for any bug fixes or improvements I may write for the five games I
>> maintain.
> =

> Kdesrc-build is able to build kde4 and kf5 if you want
> I build kde4 and kf5 on my computer with kdesrc-build it's not a problem.

On Linux, no problem.  But it took me a month or more to get kdesrc-build to
build a suite of KDE 4 software on Apple OS X.  There are definitely some
quirks in the CMake setup to be overcome on that platform=85 ;-)

Marko K=E4ning has been working on the CI for KF5/Frameworks on Apple OS X
for many more months and is only just starting to get KDE apps to run=85  T=
hat is
in a virtual environment, which, as far as I know, is exclusively KF5/Frame=
works
and Qt 5 --- no mixing with KDE 4 and Qt 4.

Cheers, Ian W.

_______________________________________________
kde-games-devel mailing list
kde-games-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-games-devel
[prev in list] [next in list] [prev in thread] [next in thread]