From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-June/006072.html | 86 ++++++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/006072.html (limited to 'zarb-ml/mageia-dev/2011-June/006072.html') diff --git a/zarb-ml/mageia-dev/2011-June/006072.html b/zarb-ml/mageia-dev/2011-June/006072.html new file mode 100644 index 000000000..f25fc2199 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006072.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] Proposal of a backporting process + + + + + + + + + +

[Mageia-dev] Proposal of a backporting process

+ Michael Scherer + misc at zarb.org +
+ Tue Jun 28 00:31:41 CEST 2011 +

+
+ +
Le mardi 28 juin 2011 à 09:55 +1200, John a écrit :
+> On Mon, 27 Jun 2011 20:17:22 +0100
+> Colin Guthrie wrote:
+
+> > That said, a GUI which detected that certain packages have come from
+> > backports and offers and easy mechanism to "switch" back to the older
+> > one from release or updates would, IMO, be a plus.
+> 
+> Rpms from Tainted have 'tainted' in the filename - why not do the same for
+> backports? Surely that would make their identification a little simpler?
+
+Detection is not that hard. If the release is superior to the one in
+release/update, this is a backport. That's trivial from a conception
+point of view.
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1