On Fri, Aug 20, 2010 at 01:46:18PM +0200, Adrian Knoth wrote:
On Fri, Aug 20, 2010 at 12:47:19PM +0200, Reinhard Tartler wrote:

> Some time back there was a little discussion about packaging Ladish > or not (www.ladish.org). Ladish is a Linux audio session manager, > which stores projects, launched apps, jack connections etc.

Why isn't it in debian yet?

By that time, it was ladish-0.1. We now have ladish-0.2, and apps need to support it, read, implement special handlers for the ladish callbacks/signals.

The newly created JACK session API aims more or less at the same, and apps need to implement it. While there is already support for JACK session in jackd1's SVN, there is none in jackd2. Nowhere.

OTOH, ladish requires a DBUS-enabled jackd, and this means jackd2 at the moment.

Long story short: This is a moving target, pure development area. The gladish screenshots look nice, but as long as there's no consensus about session save API upstream, we trick users into lots of problems: apps not supporting it, jackds not supporting it and so on.

Sounds to me like it then makes sense to do the following for Debian:

 1) Package ladish but release it only for experimental
 2) For packages supporting ladish, enable it if available at build time
 3) Build ladish-supporting packages for experimental

That way those interested in maturing ladish have a way to test progress.

Rosea: do you use gladish? I never tried it, I only saw some discussion about it on IRC and the mailing lists. I might be mistaken, so if you say it's a must have piece of software, then we clearly should get our hands dirty and start packaging it. ;)

I don't remember the details.

1e. ;) SCNR


 - 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