[Mageia-dev] Update of backport, policy proposal

Fri Jun 24 13:42:45 CEST 2011

2011/6/24 José Jorge <jjorge at free.fr>:
+> Le vendredi 24 juin 2011 02:15:03, Michael Scherer a écrit :
+>> Last solution, declare that cherry picking is not supported, or that
+>> people are on their own, and explain the reason. However, people have
+>> been asking this, and recommend this. This would also be against a goal
+>> of having confidence in the backports.
+>>
+> I have always used backports in a total way : if I want latest software
+> against stability, I take them all. Think about little dependencies that still
+> exist (vlc + ffmpeg, etc).
+>
+> So I would say Mageia has two update modes :
+>
+> - end user (security) mode (updates)
+> - power user (let's try everything) mode (updates+backports)
+>
+> Each user  will recognise himself in one of the two modes.
+
+So, where do I find myself in this scenario?
+
+I do not use backports in general, they are disabled.
+A new version of foo is coming in in cauldron and I want to use it in Mageia 1.
+A friendly packager builds a backport of this new version of foo for Mageia 1.
+I enable backports, do "urpmi foo" and I get the version from
+backports including dependencies.
+After that I disable backports.
+
+This is the way backports have been used by many users in Mandriva.
+And (BTW) this is the exact meaning of the word, a version is
+backported from a newer distrib-version or cooker/cauldron to an older
+distrib-version or current stable version.
+-- 
+wobo
+