[Mageia-dev] rehashing the faac issue

[Malo]

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