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

[Mageia-dev] Packagers meeting

+ AL13N + alien at rmail.be +
+ Wed Jun 27 13:13:54 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?
+
+Don't forget that upgrades work similarly.
+
+> 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.
+
+I think the simplest solution (code-wise) is to make sure that where-ever
+you're looking for dependencies, is to have strict requires so that it
+will always get the correct one.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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