No subject

Mon Dec 20 00:56:24 CET 2010

libanalitza into libkdeedu (or kdesupport) and then install headers so that
we can compile cantor support.
Or move cantor support into kalgebra which shouldn't be a bad idea either, I


Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Mon, Dec 20, 2010 at 10:17 PM, Jeremy Whiting=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:jpwhiting at">jpwhiting at kde.o=
rg</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"gmail_quote"><div class=3D"im">On Mon, Dec 20, 2010 at 10:59 =
AM, Niko Sams <span dir=3D"ltr">&lt;<a href=3D"mailto:niko.sams at" =
target=3D"_blank">niko.sams at</a>&gt;</span> wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1=
px solid rgb(204, 204, 204);padding-left:1ex">
<div class=3D"im">
Kde is moving towards git, and so is kdeedu. This crucial part about<br>
that are conversion<br>
rules. I wrote those rules for kdemodules including kdeedu you might<br>
want to use.<br>
<br></div><div class=3D"im">
But first you have to decide about the repository layout; should it be<br>
split or one big repository?<br>
This has to be decided by the module developers.<br>
I see one issue with split: libkdeedu. You have to make a &quot;real&quot;<=
library out of it that lives<br>
in it&#39;s own repository.<br></div><div class=3D"im">
Other than that split seems to be suitable as most/all(?) applications<br>
are independent.<br>
<br></div><div class=3D"im">
My rules produce split repositories, as I would prefer that layout.<br>
Contributing to marble<br>
would be much harder otherwise.<br>
Ok, to test the resulting repositories clone them and review the history:<b=
git clone ssh://<a href=3D"
plete/KDE/kdeedu/marble" target=3D"_blank">git at
use this to get a list of all repositories:<br>
ssh <a href=3D"mailto:git at" target=3D"_blank">git at dewey.kde.or=
g</a> ls /home/git/nsams/test-complete/KDE/kdeedu<br></div></blockquote><di=
v><br>Niko,<br><br>How would one build the sources checked out from the abo=
ve repositories?=C2=A0 Kanagram for example fails to configure because it&#=
39;s CMakeLists.txt don&#39;t have anything about KDE4 so kde4_add_app_icon=
 is not defined.=C2=A0 Is there going to be some temporary CMakeList.txt we=
 can place in a global kdeedu folder until we can fix our CMakeList.txt fil=
es to build independently?<br>
<font color=3D"#888888">
<br>Jeremy<br>=C2=A0<br></font></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padd=
ing-left:1ex"><div class=3D"im">
To access this server you need public key authentication with your<br>
<a href=3D"" target=3D"_blank"></a> =
known issue:<br>
kalgebra history doesn&#39;t go back to playground because of an svn2git<br=
bug that has<br>
been fixed already, but this version is not yet on <a href=3D"http://dewey.=" target=3D"_blank"></a>.<br>
Oh, the used rule rule is &quot;kde-ruleset/kdemodule-split-rules&quot;<br>
_______________________________________________<br></div><div class=3D"im">
kde-edu mailing list<br>
<a href=3D"mailto:kde-edu at" target=3D"_blank">kde-edu at mail.kde.=
<a href=3D"" target=3D"_blank"=
kde-edu mailing list<br>
<a href=3D"mailto:kde-edu at">kde-edu at</a><br>
<a href=3D"" target=3D"_blank"=
<br></blockquote></div><br><div>From KAlgebra side, I would be fine with sp=
litting, but then we should move libanalitza into libkdeedu (or kdesupport)=
 and then install headers so that we can compile cantor support.</div>
<div>Or move cantor support into kalgebra which shouldn&#39;t be a bad idea=
 either, I guess.</div><div><br></div><div>Aleix</div>


More information about the kde-edu mailing list