Dirk,<br><br>I got all the 4.6 branches to build as a whole kdeedu module using the attached CMakeLists.txt. I only changed the CMAKE_CURRENT_SOURCE and such in those that wouldn't build, but maybe we should change them all. At any rate, would you like me to put this simple CMakeLists.txt somewhere (svn or git) or do you just want to hold on to it until 4.6.x is done. Are we going to ship kdeedu as one tarball forever? or will 4.7 be separate tarballs?<br>
<br>thanks,<br>Jeremy<br><br><div class="gmail_quote">On Sun, May 1, 2011 at 9:30 PM, Raphael Kubo da Costa <span dir="ltr"><<a href="mailto:kubito@gmail.com">kubito@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Jeremy Whiting <<a href="mailto:jpwhiting@kde.org">jpwhiting@kde.org</a>> writes:<br>
<br>
> Where are the 4.6.3 tarballs hosted? I'd like to get a fix for the kdeedu<br>
> build issues (I made them all build individually after they were migrated to<br>
> git).<br>
<br>
</div>They're currently only available to packagers in ktown. Perhaps Dirk or<br>
someone from release-team can give you access to it.<br>
<div><div></div><div class="h5">_______________________________________________<br>
release-team mailing list<br>
<a href="mailto:release-team@kde.org">release-team@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/release-team" target="_blank">https://mail.kde.org/mailman/listinfo/release-team</a><br>
</div></div></blockquote></div><br>