On Sat, Apr 17, 2010 at 03:22:54PM -0500, Gabriel M. Beddingfield wrote:

On Sat, 17 Apr 2010, Jonas Smedegaard wrote:

stop right here.
the library and the daemon are tied together.
the protocol between jackd and libjack is NOT fixed.

(basically i consider it a mistake to even have libjack and jackd in
different packages) but it might make sense to have that.

The separation of library and daemon is so that an application can link against the library without forcing the daemon to be installed: the JACK support might be optional for that application (without it being a plugin that can be packaged separately from the main application.

When you register with libjack, it will start the daemon if it is not already running. So, you can't have the library without the daemon.[*]

That sounds like trouble: if such application is invoked inside a chroot, it causes a mess!

Debian mandates ability to enforce daemons to not be started (it is called policy.d - see e.g. the Debian package policyrcd-script-zg2 for more info (and probably somewhere in Debian Policy itself - too lazy to look it up right now).

 - Jonas

* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to