<div dir="ltr"><div dir="ltr">On Mon, Jan 20, 2025 at 6:51 AM Julius Künzel <<a href="mailto:julius.kuenzel@kde.org">julius.kuenzel@kde.org</a>> wrote:</div><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>
<div dir="ltr">
<p>19.01.2025 18:44:40 Alexander Neundorf <<a href="mailto:neundorf@kde.org" target="_blank">neundorf@kde.org</a>>:</p>
</div>
<blockquote style="margin:0px;border-left:3px solid rgb(204,204,204);padding-left:10px">
<p style="margin:0px">Hi,</p>
<br>
<p style="margin:0px">I'm wondering whether the CI images are tagged along with the KF6 releases.</p>
<p style="margin:0px">I haven't seen tags here, but maybe I looked in the wrong place:</p>
<p style="margin:0px"><a href="https://invent.kde.org/sysadmin/ci-images" target="_blank">https://invent.kde.org/sysadmin/ci-images</a></p>
<br>
<p style="margin:0px">I'm looking for that so that I could use e.g. the suse images tagged with 6.8 to do development with KDE frameworks 6.6.</p>
<br>
<p style="margin:0px">Are they tagged and I didn't see it ?</p>
<p style="margin:0px">Would it make sense ?</p></blockquote></div></div></blockquote><div><br></div><div>If we wanted to provide an "SDK" as it were that had everything needed to build KDE software then you'd probably want that to be a separate, dedicated image.</div><div>It certainly could be done though.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><blockquote style="margin:0px;border-left:3px solid rgb(204,204,204);padding-left:10px">
<br>
<p style="margin:0px">Thanks</p>
<p style="margin:0px">Alex</p>
<br>
</blockquote>
</div><span dir="ltr" style="margin-top:0px;margin-bottom:0px">Hi Alex,</span>
<br>
<br><span dir="ltr" style="margin-top:0px;margin-bottom:0px">the CI images do not contain KDE Software at all only Qt and other third-party dependencies.</span>
<br>
<br><span dir="ltr" style="margin-top:0px;margin-bottom:0px">In the CI KDE deps are pulled from a separate repository that contains artefacts of the latest CI run from all KDE software.</span></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><span dir="ltr" style="margin-top:0px;margin-bottom:0px">For local development against a certain KF version you should take a look at kde-srcbuild or kde-builder</span></div></blockquote><div><br></div><div><div>Just to add some additional detail to this - the binaries built by the CI system are only stored in that repository if they're on release branches.</div><div>Additionally, the binaries are built in full debug mode with asserts and ASAN enabled so they're extremely large, unoptimised and require the use of ASAN throughout the stack - making them and anything built with them very slow.</div><div><br></div><div>To use an example, if you were to download just what KWin provides from `make install` - without any of it's dependencies in Plasma or Frameworks - the end result is about 1GB in size.</div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
<div>
<span dir="ltr" style="margin-top:0px;margin-bottom:0px">Julius Künzel</span>
<br><span dir="ltr" style="margin-top:0px;margin-bottom:0px">KDE Developer</span>
<br><span dir="ltr" style="margin-top:0px;margin-bottom:0px">Matrix: @jlskuz:<a href="http://kde.org" target="_blank">kde.org</a></span>
<br><span dir="ltr" style="margin-top:0px;margin-bottom:0px">KDE GitLab: <a href="https://invent.kde.org/jlskuz" target="_blank">https://invent.kde.org/jlskuz</a></span></div></div></blockquote><div><br></div><div>Cheers,</div><div>Ben </div></div></div>