20 Apr
2012
20 Apr
'12
9:23 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/20/2012 02:40 PM, Martin Gräßlin wrote:
Well, logistically I guess it doesn't really matter. The only issue would be a
matter of updating kwin from the kde.org svn tree before a TDE release. From a
packaging standpoint, all current distro TDE build systems rely on getting the
code from the TDE git tree -- which makes it very convenient. For those
developing and packaging TDE, if there were a merge of twin/kwin I guess the
simplest thing to do would be to simply mirror the kwin code in the GIT tree so
that the merge is transparent to the TDE packagers, etc..
For someone to update the GIT tree with new kwin code from kde.org svn would be
fairly trivial. I would just like to prevent fragmenting the tdebase source
location for TDE. Right now, the TDE GIT repository is essentially a one-stop-shop.
- --
David C. Rankin, J.D.,P.E.
I hope this helps you understand a little bit better
how the KDE Community
works and why you should not consider "KDE" as one thing. This also explains
hopefully why e.g. the transition in kdepim has nothing to do with the desktop
and that there is no such thing as a global version. Different software has
different release cycles, that they by incident have the same version number
does not mean anything.
It does -- Thank you for taking the time to explain that.
<snip>
> I have
a practical question. If twin and kwin were to merge, how would
> that impact the current GIT hosting of the code? Would the twin code be
> included in the TDE GIT tree as a submodule our would the TDE git tree just
> receive updates from kwin as needed? Thoughts?
The best solution would be to
not host the code at all in TDE git tree. If you
use a plain kwin you could just use our release tar-balls and add the patches
from my (to be created) branch to build kwin standalone. A submodule is
probably not possible as kwin is part of a greater kde-workspace repository. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+R09IACgkQZMpuZ8CyrcgwFwCfUK8Rx3H/SXLpxSi5nm0IPlaV
LmkAn1x9+s4TOmFU+gUZ1Nj0lU19E4je
=1DWR
-----END PGP SIGNATURE-----