summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20121104/1143e595/attachment-0001.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121104/1143e595/attachment-0001.html')
-rw-r--r--zarb-ml/mageia-dev/attachments/20121104/1143e595/attachment-0001.html75
1 files changed, 75 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121104/1143e595/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121104/1143e595/attachment-0001.html
new file mode 100644
index 000000000..dbd834f7e
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20121104/1143e595/attachment-0001.html
@@ -0,0 +1,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">&lt;<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a>&gt;</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">&gt; Hi,<br>
+&gt;<br>
+&gt; I noticed we propose only the Jack2 package, but no Jack1. Yet 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/wiki/Q_differenc_jack1_jack2</a> ).<br>
+&gt;<br>
+&gt; Plus I had a very annoying bug with Ardour when using Jack2, and 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 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 &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/jack2</a> ). I saw nowhere else this &quot;jackit&quot;<br>
+&gt; naming.<br>
+&gt;<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 &quot;jackit&quot; ....<br>
+<div class="im">&gt; So I am questioning the naming of this existing package, and 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 &quot;libjack-devel&quot;.<br>
+&gt;<br>
+&gt; I think that none of the names are really fit IMO. First jackit 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 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>
+</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&#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>
+</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 &quot;Provides: jackit&quot; so that it works as an alternative to Jack2 (for instance for Ardour)?<br>
+
+Thanks.<br><br>Jehan<br></div>