[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[LCFC] templates://jack-audio-connection-kit/{jackd.templates}



This is the last call for comments for the review of debconf
templates for jack-audio-connection-kit.

The reviewed templates will be sent on Tuesday, October 06, 2009 to the package
maintainer as a bug report and a mail will be sent to this list with
"[BTS]" as a subject tag.


-- 
Jonathan Wiltshire

1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3  A903 CA6B EA3E DB80 0B52
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
Source: jack-audio-connection-kit
Section: sound
Priority: optional
Maintainer: Debian Multimedia Maintainers <pkg-multimedia-maintainers@lists.alioth.debian.org>
Uploaders: Guenter Geiger (Debian/GNU) <geiger@debian.org>,
	   Junichi Uekawa <dancer@debian.org>,
	   Free Ekanayaka <freee@debian.org>,
	   Reinhard Tartler <siretart@tauware.de>,
	   Adrian Knoth <adi@drcomp.erfurt.thur.de>
Build-Depends: cdbs,
	       type-handling,
	       debhelper (>= 7.0.0),
	       patchutils,
	       dh-buildinfo,
	       libasound2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
	       libsndfile1-dev,
	       doxygen,
	       automake,
	       libtool,
	       libreadline5-dev,
	       libraw1394-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
	       libfreebob0-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
	       libsamplerate-dev,
	       po-debconf,
	       libcelt-dev,
	       libffado-dev [amd64 i386 powerpc]
Standards-Version: 3.8.2
Homepage: http://jackaudio.org/
Vcs-Git: git://git.debian.org/git/pkg-multimedia/jack-audio-connection-kit.git
Vcs-Browser: http://git.debian.org/?p=pkg-multimedia/jack-audio-connection-kit.git;a=summary

Package: jackd
Architecture: any
Depends: ${shlibs:Depends},
	 ${misc:Depends},
	 coreutils (>= 4.0),
	 debconf | debconf-2.0,
	 libjack0 (= ${binary:Version})
Recommends: qjackctl,
	    libpam-modules,
	    jackd-firewire [amd64 i386 powerpc]
Suggests: jack-tools,
	  meterbridge,
	  libjackasyn0
Description: JACK Audio Connection Kit (server and example clients)
 JACK is a low-latency sound server, allowing multiple applications to
 connect to one audio device, and to share audio between themselves.
 .
 This package contains the daemon jackd as well as some example clients.

Package: libjack0
Architecture: any
Section: libs
Depends: ${shlibs:Depends},
	 ${misc:Depends}
Conflicts: jackd (>> ${binary:Version}),
	   jackd (<< ${binary:Version})
Suggests: jackd (= ${binary:Version})
Description: JACK Audio Connection Kit (libraries)
 JACK is a low-latency sound server, allowing multiple applications to
 connect to one audio device, and to share audio between themselves.
 .
 This package contains the shared libraries.

Package: jackd-firewire
Architecture: amd64 i386 powerpc
Depends: ${shlibs:Depends},
	 ${misc:Depends},
	 jackd (= ${binary:Version})
Description: JACK Audio Connection Kit (FFADO and FreeBoB backends)
 JACK is a low-latency sound server, allowing multiple applications to
 connect to one audio device, and to share audio between themselves.
 .
 This package contains the IEEE1394 (FireWire) backends FFADO and FreeBoB.

Package: libjack-dev
Architecture: any
Section: libdevel
Depends: libjack0 (= ${binary:Version}),
	 ${asound:Depends},
	 pkg-config,
	 ${misc:Depends},
	 ${shlibs:Depends}
Provides: libjack0.100.0-dev
Description: JACK Audio Connection Kit (development files)
 JACK is a low-latency sound server, allowing multiple applications to
 connect to one audio device, and to share audio between themselves.
 .
 This package contains files needed for the development of JACK applications
 and an API reference.
Template: jackd/tweak_rt_limits
Type: boolean
Default: false
_Description: Enable realtime process priority?
 If you want to run jackd with realtime priorities, the user starting jackd
 needs realtime permissions. Accept this option to create the
 file /etc/security/limits.d/audio.conf, granting realtime
 priority and memlock privileges to the audio group.
 .
 Running jackd with realtime priority minimizes latency, but
 may lead to complete system lock-ups by requesting
 all the available physical system memory, which is unacceptable in
 multi-user environments.

Reply to: