[Mageia-dev] KDE SC 4.7.3

Thu Nov 3 13:40:36 CET 2011

2011/11/3 Dark Charlot <jcldc13 at gmail.com>:
+[...]
+>> >  So what it's your opinion about that ?
+>> If we need to backport something then in all case it would be better
+>> to backport the 4.7.5 release just for avoid later the
+>> « could you please backport 4.7.4 & then 4.7.5 etc etc ».
+>
+>  Well I am a profane in packaging and I do not know the amount of work to
+> package a new kde 4.x.x release, but you seem to be very efficient in this
+> task. Maybe I am wrong but kde packaging looks like now something more or
+> less
+> straightforward, I mean automatic ?
+It's no automatic at all :o) : i usually build for bold arch the whole
+KDE before
+even committing on the svn, so while it seems « easy » if you're just following
+pkgsubmit.mageia.org it's also mean that i test before that build is
+working *but*
+ also that upgrade is working as expected.
+Also when asking for backport you should check first our backport policy (this
+mean we need to have a QA on the whole stuff & since our QA team is quite small
+and have better priority then testing the whole KDE for backport issue).
+I'm still wondering btw how we'll deal with the kdepim upgrade between
+kmail2 so...
+
+
+>So why not backporting since now and for
+> every kde 4.7.X release to mageia1, it will make a lot of people happy :).
+*I* won't backport it as said earlier currently, i don't prevent anyone to do it
+but since KDE is *quite* important i'm not sure it's wise to do it currently
+(cf above ).
+
+> One more time, I am not probably aware about the amount of work it
+> implies.... Anyway thanks.
+
+Well you can maybe try to do it by yourself following at least the build order
+of the src.rpm i put on the mageia wiki.
+
+
+
+-- 
+Balcaen John
+Jabber-id: mikala at jabber.littleboboy.net
+