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/016441.html | 97 ++++++++++++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016441.html (limited to 'zarb-ml/mageia-dev/2012-June/016441.html') diff --git a/zarb-ml/mageia-dev/2012-June/016441.html b/zarb-ml/mageia-dev/2012-June/016441.html new file mode 100644 index 000000000..2687aad20 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016441.html @@ -0,0 +1,97 @@ + + + + [Mageia-dev] Proposed Feature:Backports_update_applet + + + + + + + + + +

[Mageia-dev] Proposed Feature:Backports_update_applet

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Jun 12 18:46:41 CEST 2012 +

+
+ +
On Sat, 09 Jun 2012, andre999 wrote:
+
+>>    
+> You got me thinking :)
+> - Just marking all backport repos as update repos is almost enough to solve 
+> the problem, in terms of the tools installing the backports.  Great idea !
+> We just have to tweak the tools so that a backport is only installed as an 
+> update of a backport.
+
+No. People who only want to use a specific backport will not enable the
+backport repository. They will install the backport and keep the
+backports repository disabled.
+
+>
+> - Note that we should allow a non-backport to replace a backport, as will 
+> likely be encountered in a release update.  If the versioning is properly 
+> done (according to established packaging policy), a non-backport in a newer 
+> release will have a higher version number, thus replacing the backport.
+
+Which policy ?
+
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

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