I believe it did, but I also think only part of it got applied and committed, we can look in the ml history and see. Most apps look trivial (adding a few macros to their CMakeLists.txt like kbruch did. the ones using libkeduvocdocument will need some special consideration, but again shouldn't be hard. Also, once one is working the others can be done the same. I think there are two big things we need to be sure of.<br>
<br>1) The python stuff in the top level CMakeLists.txt for marble gets into the marble cmakelists.txt<br>2) We put docs somewhere reasonable. Are we going to put docs with the apps? or in a kdeedu-docs repository?<br><br>
1 can and probably already is solvable by the marble devs I bet. 2 I'm not sure about. On one hand, keeping the docs with the application make it easy for distros that package apps separate to keep the docs in the app's package. On the other hand, any documentation editors will have to clone many repos to edit docs.<br>
<br>Jeremy<br><br><div class="gmail_quote">On Thu, Feb 3, 2011 at 4:15 PM, Daniel Laidig <span dir="ltr"><<a href="mailto:laidig@kde.org">laidig@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thursday 03 February 2011 22:56:13 Peter Hedlund wrote:<br>
> On Feb 3, 2011, at 11:51 AM, Anne-Marie Mahfouf wrote:<br>
> > Hi KDE-Edu devels,<br>
> ><br>
> > Now that kdelibs and kdebase have been moved to git, the rest of KDE will<br>
> > soon follow. Ian "eean" kindly offered to write the rules for kdeedu,<br>
> > thanks to him!<br>
> ><br>
> > Before the move we need to ensure that all subprojects build standalone<br>
> > (without breaking the overall kdeedu build as well).<br>
> > KBruch maintainer Sebastian did that earlier today<br>
> > <a href="http://websvn.kde.org/trunk/KDE/kdeedu/kbruch/CMakeLists.txt?r1=1009581&r" target="_blank">http://websvn.kde.org/trunk/KDE/kdeedu/kbruch/CMakeLists.txt?r1=1009581&r</a><br>
> > 2=1218675<br>
> ><br>
> > While it's easy for small projects, it is probably a bit more work for<br>
> > Marble which is more complex. Can the Marble team look into it quite<br>
> > quickly? Any problems can be discussed here and if necessary we'll ask<br>
> > for help. Same for KStars.<br>
> > We also need to take care of the libs as we discussed and noted on<br>
> > <a href="http://community.kde.org/KDE_Edu#Git_Migration" target="_blank">http://community.kde.org/KDE_Edu#Git_Migration</a><br>
><br>
> Without cmake and library development skills it's definitely the handling<br>
> of the keduvocdocument lib that is giving me problems. Either we keep all<br>
> applications using it together or I/we need help making a proper library<br>
> out of it.<br>
<br>
</div>What happened to the patch Niko Sams wrote in December? Didn't it already do<br>
all this (i.e. create proper libraries and cmake modules and make apps build<br>
standalone)?<br>
<div><div></div><div class="h5"><br>
> Anne-Marie, how do you plan to handle KHangMan since it is one of the<br>
> programs using it?<br>
><br>
> Thanks,<br>
> Peter<br>
><br>
><br>
> _______________________________________________<br>
> kde-edu mailing list<br>
> <a href="mailto:kde-edu@mail.kde.org">kde-edu@mail.kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/kde-edu" target="_blank">https://mail.kde.org/mailman/listinfo/kde-edu</a><br>
_______________________________________________<br>
kde-edu mailing list<br>
<a href="mailto:kde-edu@mail.kde.org">kde-edu@mail.kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-edu" target="_blank">https://mail.kde.org/mailman/listinfo/kde-edu</a><br>
</div></div></blockquote></div><br>