diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html b/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html new file mode 100644 index 000000000..fad5bcf08 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html @@ -0,0 +1,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"><<a href="mailto:andre999mga@laposte.net" target="_blank">andre999mga@laposte.net</a>></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"> +<<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a> <mailto:<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@<u></u>laposte.net</a>>> wrote:<br> + + +<br> + Jehan Pagès a écrit :<br> + > Hi,<br> + ><br> + > I noticed we propose only the Jack2 package, but no Jack1. Yet<br> + 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/<u></u>wiki/Q_differenc_jack1_jack2</a> ).<br> + ><br> + > Plus I had a very annoying bug with Ardour when using Jack2, and<br> + 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<br> + 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<br> + "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/<u></u>jack2</a> ). I saw nowhere else this<br> + "jackit"<br> + > naming.<br> + ><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 "jackit" ....<br> + > So I am questioning the naming of this existing package, and<br> + 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<br> + "libjack-devel".<br> + ><br> + > I think that none of the names are really fit IMO. First jackit<br> + 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<br> + 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> + 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> +<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 "Provides: jackit" 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> + "jack1 - the Jack Audio Connection Kit 1"<br> +and modify the description to include :<br> + "This is the original C implementation of the Jack Audio Connection Kit protocol (JACK). It is under active development concurrently with jackit (JACK2)"<br> +<br></blockquote><div><br>I'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'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> |