21 Apr
2012
21 Apr
'12
6:20 a.m.
On Friday 20 April 2012 16:23:30 David C. Rankin wrote:
KDE does not have an "svn tree" any more. It's all git
nowadays.
Cheers
Martin
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.
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.