On Thursday 03 of May 2012 23:51:44 Francois Andriot wrote:
Amarok:
I have some FTBFS and some features added.
See
http://bugs.trinitydesktop.org/show_bug.cgi?id=984
I also incorporate
I also incorporate
Kdeadmin:
I've just added a patch to add support for RHEL/Fedora in networkconf
backend, see:
See
http://bugs.trinitydesktop.org/show_bug.cgi?id=619
I also incorporate
Kdebase:
Too many patches to compare ! I think the only ones I have that you
don't are RHEL/Fedora specific, so they won't go upstream.
An important point is the famous "startkde" script. Should we try to
have a stable updated script upstream, or should we keep distro-specific
changes in every packaging ?
I am definitely for it to have stable upstream updated script. And to solve
specific distribution in it. I do not know how big parts are the distribution
specific. But I believe it would go through to resolve by the conditions, or
spin-off into a separate "include".
Kdegraphics:
I have some FTBFS on stock 3.5.13.
See
http://bugs.trinitydesktop.org/show_bug.cgi?id=984
I also incorporate
Kdelibs:
You do not have patch for bugs: 656 , 764
You do not have patch for commits: 24f144fa , 2b035349
I also incorporate
Kdeutils:
The "klaptopdaemon" from upstream will only work on debian/ubuntu
because there is a hardcoded "dpkg" command in its source code.
For all other distros, you should apply the following patch (should be
upstream IMHO):
http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/kdeutils/kdeut
ils-3.5.13-klaptopdaemon_dpkg_command.patch
I also incorporate
That's all what I see for now.
Good job BTW :-)
Francois
Thank you for comparing patches. I have added to their packages remaining
gcc-4.7 patches. And patches for reorganization of the menu. Do I have to
compile and test...
Slavek
--