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
|
Hi,<br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 3, 2012 at 11:11 PM, PhilippeDidier <span dir="ltr"><<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Jehan Pagès a écrit :<br>
<div class="im">> Hi,<br>
><br>
> I noticed we propose only the Jack2 package, but no Jack1. Yet Jack2 is<br>
> simply another implementation in C++ of the Jack protocol, and not a<br>
> newer version (as the official website also states clearly:<br>
> <a href="http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2" target="_blank">http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2</a> ).<br>
><br>
> Plus I had a very annoying bug with Ardour when using Jack2, and people<br>
> on Ardour mailing list told me it was a known issue with Jack2 (both<br>
> Ardour and Jack2 were installed from the Mageia 2 packages). I compiled<br>
> Jack1, and it indeed fixed the issue.<br>
><br>
> So I am thinking on proposing a spec for Jack1.<br>
><br>
> But then I have questions:<br>
><br>
> 1/ How should I name this package? The jack2 package is named "jackit"<br>
> and I have no idea where you got that from (I guess this is a shorter<br>
> name for "Jack Audio Connection Kit", but should we really change<br>
> package names this way?<br>
> It is not that long). The official alternative<br>
> name of Jack2 is "jackdmp" (see README here:<br>
> <a href="https://github.com/jackaudio/jack2" target="_blank">https://github.com/jackaudio/jack2</a> ). I saw nowhere else this "jackit"<br>
> naming.<br>
><br>
</div>We inherit this from Mandrake : in the early years of Mandrake a jack<br>
package already existed but it had nothing to do with JACK (Jack Audio<br>
Connexion Kit) : it was a console frontend for cd rippers, still<br>
provided in Mageia...<br>
<br>
When JACK was imported into Mandrake it had to be given an other name...<br>
so jackit !!!<br>
There was a tonic controversy on Mandrake forum about this in 2003 or<br>
2004 year.<br>
Mandrake and then Mandriva and and then Mageia are the only<br>
distributions calling JACK package "jackit" ....<br>
<div class="im">> So I am questioning the naming of this existing package, and would like<br>
> to propose some rename along with a new name for a Jack1 package.<br>
> Maybe simply "jack1" and "jack2"? Or "jack" and "jackdmp"?<br>
><br>
> 2/ How should the virtual dependency be named?<br>
> The existing "jackit" spec provides a "jackit-devel" and a "libjack-devel".<br>
><br>
> I think that none of the names are really fit IMO. First jackit for the<br>
> same reason as before (I don't see where this name comes from), also<br>
> libjack (and the -devel suffix) because this kit is not *only* a library<br>
> (there are also the jackd daemon, tools, etc.).<br>
><br>
> I propose simply "jack" as virtual package name.<br>
><br>
> How does this sound?<br>
> Thanks.<br>
><br>
> Jehan<br>
</div>Not simple because of this context ...<br>
If you want to call JACK jack you need to remove first the existing jack<br>
from the repo, and to modify the spec for every package requiring jackit<br>
now, to make them require jack if it is the new package name for JACK .<br>
<br>
Post Scriptum : Reading this I don't know if my explanation is clear<br>
enough ...<br>
A key to understand what I wrote :<br>
"jack" is the name of a package (whatever its content is)<br>
"jackit" is the name of a package<br>
"JACK" is the recursive acronym (Jack Audio Connexion Kit) of the<br>
software you are talking about<br>
<br>
</blockquote></div><br>Ok I understood the deal.<br>I would personally prefer even a longer package name like jack-audio-connection-kit. Mageia would gain from having clearer naming. Especially if we add the Jack1 alternative.<br>
<br>Now if this is a big deal, and it generates a controversy again, it is not that a big deal. The question thus is: how do I call Jack1 package then? And can I say that this new package "Provides: jackit" so that it works as an alternative to Jack2 (for instance for Ardour)?<br>
Thanks.<br><br>Jehan<br></div>
|
