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

List:       kde-panel-devel
Subject:    Plamsa Stable Build.kde.org failures
From:       David Edmundson <david () davidedmundson ! co ! uk>
Date:       2016-06-30 12:50:02
Message-ID: CAGeFrHAGzJxA5gs_b2AB6G3jPGv36fqcnLxrUo55uFT9R+1+QA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I wanted to write up why Plasma stable is failing on CI so that we have a
written down record. (and so we don't keep getting told off by sysadmins
for not fixing it)

Plasma 5.7 requires Qt 5.6
The "stable-kf5-qt5 " layer on CI  builds against Qt 5.5

*Can we set Plasma stable to use latest Qt/Frameworks (the kf5-qt5 layer
master uses):*

Yes, but:
[10:06] <bcooksley> you'll just end up without a CI on your master


*Can we update the stable-kf5-qt5 layer to use a newer Qt:*
Not without upping the Qt used by Applications/16.04

*Could we add another layer:*

[10:04] <bcooksley> new layer is even more painful
[10:04] <bcooksley> requires adjusting the DSL
[10:04] <bcooksley> and building Qt another time
[10:05] <bcooksley> plus all of Frameworks
[10:05] <bcooksley> and anything else which Plasma happens to need in there

*Is there a long term plan:*

Michael Pyne/Ben have a thread redesigning logical-module-strucutre in that
long email thread somewhere. See thread
"Proposal to improving KDE Software Repository Organization"


*Is there a short term plan:*

Personally I think our our only viable short term options are:
 -  forcing Qt5.6 on the stable branches of applications. Theoretically it
won't break anything (though in practice who knows)
 - turning off the CI for Plasma stable for now.

I'm not sure what other options there are.

David

[Attachment #5 (text/html)]

<div dir="ltr"><div><div><div>I wanted to write up why Plasma stable is failing on CI \
so that we have a written down record. (and so we don&#39;t keep getting told off by \
sysadmins for not fixing it)<br><br></div><div>Plasma 5.7 requires Qt \
5.6<br></div><div>The &quot;stable-kf5-qt5 &quot; layer on CI   builds against Qt \
5.5</div><div><br><b>Can we set Plasma stable to use latest Qt/Frameworks (the \
kf5-qt5 layer master uses):</b><br><br>Yes, but:<br><div>[10:06] &lt;bcooksley&gt; \
you&#39;ll just end up without a CI on your master<br><br></div><div><br><b>Can we \
update the stable-kf5-qt5 layer to use a newer Qt:</b><br></div><div>Not without \
upping the Qt used by Applications/16.04<br></div><div><br></div></div><b>Could we \
add another layer:</b><br><br>[10:04] &lt;bcooksley&gt; new layer is even more \
painful<br>[10:04] &lt;bcooksley&gt; requires adjusting the DSL<br>[10:04] \
&lt;bcooksley&gt; and building Qt another time<br>[10:05] &lt;bcooksley&gt; plus all \
of Frameworks<br>[10:05] &lt;bcooksley&gt; and anything else which Plasma happens to \
need in there<br><br></div><div><b>Is there a long term plan:</b><br><br>Michael \
Pyne/Ben have a thread redesigning logical-module-strucutre in that long email thread \
somewhere. See thread<br>&quot;Proposal to improving KDE Software Repository \
Organization&quot;<br><br><br></div><div><b>Is there a short term \
plan:</b><br><br></div><div>Personally I think our our only viable short term options \
are:<br>  -   forcing Qt5.6 on the stable branches of applications. Theoretically it \
won&#39;t break anything (though in practice who knows)<br></div><div>  - turning off \
the CI for Plasma stable for now.<br></div><div><br>I&#39;m not sure what other \
options there are.<br><br></div><div>David<br></div><div><br></div><div><br></div></div></div>



[Attachment #6 (text/plain)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


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