1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] rehashing the faac issue
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rehashing%20the%20faac%20issue&In-Reply-To=%3C508F91B2.8030707%40rhul.ac.uk%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="019641.html">
<LINK REL="Next" HREF="019647.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] rehashing the faac issue</H1>
<B>Malo</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rehashing%20the%20faac%20issue&In-Reply-To=%3C508F91B2.8030707%40rhul.ac.uk%3E"
TITLE="[Mageia-dev] rehashing the faac issue">pierre-malo.denielou at rhul.ac.uk
</A><BR>
<I>Tue Oct 30 09:37:06 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="019641.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019647.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19645">[ date ]</a>
<a href="thread.html#19645">[ thread ]</a>
<a href="subject.html#19645">[ subject ]</a>
<a href="author.html#19645">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 30/10/12 08:20, Guillaume Rousse wrote:
><i> Le 30/10/2012 01:34, Frank Griffin a écrit :
</I>>><i> On 10/29/2012 06:20 PM, Olivier Blin wrote:
</I>>>><i> I would prefer B: adding a nonfree-tainted repo (+ its
</I>>>><i> updates/testing/backports/debug brothers). See
</I>>>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2833">https://bugs.mageia.org/show_bug.cgi?id=2833</A> for a list of packages
</I>>>><i> needing faac. Yes, that's overkill, it will clutter the urpmi media
</I>>>><i> config UI, but that's the only clean way we have. I guess a simple way
</I>>>><i> to unclutter the drakrpm-edit-media UI would be to add a drop-down
</I>>>><i> menu to select between "Release + Updates" (default and most commonly
</I>>>><i> used media), "Updates Testing", "Backports" (whenever it gets in), and
</I>>>><i> "Debug" (for debug packages of all aforementioned groups).
</I>>><i> I don't know what's involved in this, but it is certainly the optimal
</I>>><i> solution.
</I>><i> Creating a specific workflow (a new buildsystem queue, a new entry in
</I>><i> package manager configuration, etc...) for a category of packages with a
</I>><i> unique candidate is not precisely something I'd call 'optimal'. Unless
</I>><i> in term of complexity.
</I>><i>
</I>><i> Morevoer, unless someone volonteers to actually implement it in our
</I>><i> buildsystem, that's a purely hypothetical solution.
</I>
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
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="019641.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI>Next message: <A HREF="019647.html">[Mageia-dev] rehashing the faac issue
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19645">[ date ]</a>
<a href="thread.html#19645">[ thread ]</a>
<a href="subject.html#19645">[ subject ]</a>
<a href="author.html#19645">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|