summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html
blob: fad5bcf08bd7a92907300b7db99791753b7d1630 (plain)
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
Hi,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 4, 2012 at 4:29 AM, andre999 <span dir="ltr">&lt;<a href="mailto:andre999mga@laposte.net" target="_blank">andre999mga@laposte.net</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jehan Pagès a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br><div class="im">
On Sat, Nov 3, 2012 at 11:11 PM, PhilippeDidier<br></div><div><div class="h5">
&lt;<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a> &lt;mailto:<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@<u></u>laposte.net</a>&gt;&gt; wrote:<br>


<br>
    Jehan Pagès a écrit :<br>
     &gt; Hi,<br>
     &gt;<br>
     &gt; I noticed we propose only the Jack2 package, but no Jack1. Yet<br>
    Jack2 is<br>
     &gt; simply another implementation in C++ of the Jack protocol, and not a<br>
     &gt; newer version (as the official website also states clearly:<br>
     &gt; <a href="http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2" target="_blank">http://trac.jackaudio.org/<u></u>wiki/Q_differenc_jack1_jack2</a> ).<br>
     &gt;<br>
     &gt; Plus I had a very annoying bug with Ardour when using Jack2, and<br>
    people<br>
     &gt; on Ardour mailing list told me it was a known issue with Jack2 (both<br>
     &gt; Ardour and Jack2 were installed from the Mageia 2 packages). I<br>
    compiled<br>
     &gt; Jack1, and it indeed fixed the issue.<br>
     &gt;<br>
     &gt; So I am thinking on proposing a spec for Jack1.<br>
     &gt;<br>
     &gt; But then I have questions:<br>
     &gt;<br>
     &gt; 1/ How should I name this package? The jack2 package is named<br>
    &quot;jackit&quot;<br>
     &gt; and I have no idea where you got that from (I guess this is a shorter<br>
     &gt; name for &quot;Jack Audio Connection Kit&quot;, but should we really change<br>
     &gt; package names this way?<br>
     &gt; It is not that long). The official alternative<br>
     &gt; name of Jack2 is &quot;jackdmp&quot; (see README here:<br>
     &gt; <a href="https://github.com/jackaudio/jack2" target="_blank">https://github.com/jackaudio/<u></u>jack2</a> ). I saw nowhere else this<br>
    &quot;jackit&quot;<br>
     &gt; naming.<br>
     &gt;<br>
    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 &quot;jackit&quot; ....<br>
     &gt; So I am questioning the naming of this existing package, and<br>
    would like<br>
     &gt; to propose some rename along with a new name for a Jack1 package.<br>
     &gt; Maybe simply &quot;jack1&quot; and &quot;jack2&quot;? Or &quot;jack&quot; and &quot;jackdmp&quot;?<br>
     &gt;<br>
     &gt; 2/ How should the virtual dependency be named?<br>
     &gt; The existing &quot;jackit&quot; spec provides a &quot;jackit-devel&quot; and a<br>
    &quot;libjack-devel&quot;.<br>
     &gt;<br>
     &gt; I think that none of the names are really fit IMO. First jackit<br>
    for the<br>
     &gt; same reason as before (I don&#39;t see where this name comes from), also<br>
     &gt; libjack (and the -devel suffix) because this kit is not *only* a<br>
    library<br>
     &gt; (there are also the jackd daemon, tools, etc.).<br>
     &gt;<br>
     &gt; I propose simply &quot;jack&quot; as virtual package name.<br>
     &gt;<br>
     &gt; How does this sound?<br>
     &gt; Thanks.<br>
     &gt;<br>
     &gt; Jehan<br>
    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&#39;t know if my explanation  is clear<br>
    enough ...<br>
    A key to understand what I wrote :<br>
    &quot;jack&quot; is the name of a package (whatever its content is)<br>
    &quot;jackit&quot; is the name of a package<br>
    &quot;JACK&quot; is the recursive acronym (Jack Audio Connexion Kit) of the<br>
    software you are talking about<br>
<br>
<br>
Ok I understood the deal.<br>
I would personally prefer even a longer package name like<br>
jack-audio-connection-kit. Mageia would gain from having clearer naming.<br>
Especially if we add the Jack1 alternative.<br>
<br>
Now if this is a big deal, and it generates a controversy again, it is<br>
not that a big deal. The question thus is: how do I call Jack1 package<br>
then? And can I say that this new package &quot;Provides: jackit&quot; so that it<br>
works as an alternative to Jack2 (for instance for Ardour)?<br>
Thanks.<br>
<br>
Jehan<br>
</div></div></blockquote>
<br>
why not give jack1 the name :<br>
 &quot;jack1 - the Jack Audio Connection Kit 1&quot;<br>
and modify the description to include :<br>
 &quot;This is the original C implementation of the Jack Audio Connection Kit protocol (JACK).  It is under active development concurrently with jackit (JACK2)&quot;<br>
<br></blockquote><div><br>I&#39;ll do this like this, then, and propose a SPEC to my mentor, maybe today.<br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">


It might also be a good idea to modify the jackit description to indicate that it is concurrent to jack1 as well.<br>
And maybe rename it to jack2, if it is not too complicated ?<br>
<br></blockquote><div><br>I guess the maintainer of this package will have to do this. I&#39;ll search for his email.<br>Thanks all.<br><br>Jehan<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">


We could always use provides to accommodate packages requiring JACK.<br>
<br>
Just some suggestions ...<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
André<br>
</font></span></blockquote></div><br></div>