diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121103/ce0b501b/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20121103/ce0b501b/attachment.html | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121103/ce0b501b/attachment.html b/zarb-ml/mageia-dev/attachments/20121103/ce0b501b/attachment.html new file mode 100644 index 000000000..a34a5e0b9 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121103/ce0b501b/attachment.html @@ -0,0 +1,11 @@ +Hi,<br><br>I noticed we propose only the Jack2 package, but no Jack1. Yet Jack2 is simply another implementation in C++ of the Jack protocol, and not a newer version (as the official website also states clearly: <a href="http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2">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 on Ardour mailing list told me it was a known issue with Jack2 (both Ardour and Jack2 were installed from the Mageia 2 packages). I compiled 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" and I have no idea where you got that from (I guess this is a shorter name for "Jack Audio Connection Kit", but should we really change package names this way? It is not that long). The official alternative name of Jack2 is "jackdmp" (see README here: <a href="https://github.com/jackaudio/jack2">https://github.com/jackaudio/jack2</a> ). I saw nowhere else this "jackit" naming.<br> + +<br>So I am questioning the naming of this existing package, and would like 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 same reason as before (I don't see where this name comes from), also libjack (and the -devel suffix) because this kit is not *only* a library (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> |