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-October/019645.html | 100 ++++++++++++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-October/019645.html (limited to 'zarb-ml/mageia-dev/2012-October/019645.html') diff --git a/zarb-ml/mageia-dev/2012-October/019645.html b/zarb-ml/mageia-dev/2012-October/019645.html new file mode 100644 index 000000000..3d83c37b0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-October/019645.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] rehashing the faac issue + + + + + + + + + +

[Mageia-dev] rehashing the faac issue

+ Malo + pierre-malo.denielou at rhul.ac.uk +
+ Tue Oct 30 09:37:06 CET 2012 +

+
+ +
On 30/10/12 08:20, Guillaume Rousse wrote:
+> Le 30/10/2012 01:34, Frank Griffin a écrit :
+>> On 10/29/2012 06:20 PM, Olivier Blin wrote:
+>>> I would prefer B: adding a nonfree-tainted repo (+ its
+>>> updates/testing/backports/debug brothers). See
+>>> https://bugs.mageia.org/show_bug.cgi?id=2833 for a list of packages
+>>> needing faac. Yes, that's overkill, it will clutter the urpmi media
+>>> config UI, but that's the only clean way we have. I guess a simple way
+>>> to unclutter the drakrpm-edit-media UI would be to add a drop-down
+>>> menu to select between "Release + Updates" (default and most commonly
+>>> used media), "Updates Testing", "Backports" (whenever it gets in), and
+>>> "Debug" (for debug packages of all aforementioned groups).
+>> I don't know what's involved in this, but it is certainly the optimal
+>> solution.
+> Creating a specific workflow (a new buildsystem queue, a new entry in
+> package manager configuration, etc...) for a category of packages with a
+> unique candidate is not precisely something I'd call 'optimal'. Unless
+> in term of complexity.
+>
+> Morevoer, unless someone volonteers to actually implement it in our
+> buildsystem, that's a purely hypothetical solution.
+
+I'd have to go with Guillaume on that one.
+The inclusion of faac came up a long time ago, and the simple logical 
+answer is to created a tainted-non-free repos.
+
+However, the three problems with that solution are:
+- there is only a handful of people at Mageia who can do that, and none 
+of them actually did it.
+- there is only faac, so why bother? (fuelling the first reason)
+- the reason that philippe mentioned: is having 3 versions of each 
+multimedia package really worth it? ...
+
+Cheers,
+-- 
+Malo
+
+ + + + + + + + + + + +
+

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