questions regarding our policy

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

reading through our policy once again [1], two (unrelated) questions (so
please forgive me for addressing both in the same mail) sprang to my eye.

#1 "1.6. midi"
there are ideas about using /usr/share/debian-multimedia/midi/ and/or
/etc/debian-multimedia/midi/ for specifying (default) midi connections.

did anybody ever implement that?
i couldn't find anything like that on my harddisk (which i believe has
plenty of multimedia packages installed :-))



#2 "1.4 sound input/output selection"
it clearly says: "the applications should not start jack/... daemon
themselves".

however, if the application is using the jack API call
"jack_client_open()" without special flags, this will automatically
start the jackd server if it is not already running.
so the question is, whether applications should indeed avoid starting
jackd (e.g. by passing the "JackNoStartServer" flag to the
jack_client_open() call) or whether the policy is a bit unprecise here
and (should) only request(s) to not try to start the daemon if it is
already running.
i don't know when this part of the policy was written, it might be well
before the advent of the jack_client_open() function; in the olde days
there was only jack_client_new() which would _not_ automagically start
the jackd if needed.


mgfdad
IOhannes



[1] http://wiki.debian.org/DebianMultimedia/Policy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3kvZ0ACgkQkX2Xpv6ydvQQ0QCdFdXFRTMni4U5i4UunLwCYr/2
P5IAn2EzWns18Lh7ErHvK7+Z93ZJo9BU
=VAjA
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20110531/9bc0efb7/attachment.bin>