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/016902.html | 127 +++++++++++++++++++++++++++++++ 1 file changed, 127 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016902.html (limited to 'zarb-ml/mageia-dev/2012-June/016902.html') diff --git a/zarb-ml/mageia-dev/2012-June/016902.html b/zarb-ml/mageia-dev/2012-June/016902.html new file mode 100644 index 000000000..052ae8e3b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016902.html @@ -0,0 +1,127 @@ + + + + [Mageia-dev] Packagers meeting + + + + + + + + + +

[Mageia-dev] Packagers meeting

+ Rémi Verschelde + remi at verschelde.fr +
+ Wed Jun 27 13:00:04 CEST 2012 +

+
+ +
2012/6/27 Sander Lepik <sander.lepik at eesti.ee>:
+> I still don't understand where's the big problem if we enable release media for updates.
+> It's not updated, so it shouldn't slow down updating too much. Hardware that can run DEs
+> today should have no problems with release media enabled for updates. QA is proposing this
+> solution again and again. Is this really that hard to change?
+
+The _simplest_ solution (conceptually speaking) would be to use a
+condition which would enable release media for updates _if_ one or
+more of the dependancies cannot be found in the updates media.
+But I guess that it's not that simple in the code if it still has not
+been considered otherwise than conceptually.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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