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/2012-June/016317.html | 123 +++++++++++++++++++++++++++++++ 1 file changed, 123 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016317.html (limited to 'zarb-ml/mageia-dev/2012-June/016317.html') diff --git a/zarb-ml/mageia-dev/2012-June/016317.html b/zarb-ml/mageia-dev/2012-June/016317.html new file mode 100644 index 000000000..565e22ec5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016317.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] Backports policy clarification (and discussion) + + + + + + + + + +

[Mageia-dev] Backports policy clarification (and discussion)

+ blind Pete + 0123peter at gmail.com +
+ Sat Jun 9 10:50:49 CEST 2012 +

+
+ +
Sander Lepik wrote:
+
+> 09.06.2012 10:06, blind Pete kirjutas:
+>> andre999 wrote:
+>>
+>> [snip]
+>>> I see your point.
+>>> In most cases, a backport for mga1 would be essentially identical for
+>>> mga2 (except package file name and corresponding changes in the spec
+>>> file). It would only differ if dependancies differ, which I suspect is
+>>> unlikely for wesnoth or most other games, for example.
+>>> So this means that for a backport to mga1, we should first do one to
+>>> mga2.
+>> [snip]
+>>
+>> No.  Cauldron then mga2 then mga1.
+>>
+> Well, you can't do backport for mga2 if you don't have new version in
+> cauldron ;)
+
+Just trying to be complete.  This is the sort of situation where 
+incompleteness becomes ambiguity which becomes a bug.  
+
+-- 
+blind Pete
+Sig goes here...  
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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