On Dec 20, 2009, at 4:05 AM, Adrian Prantl <[email protected]> wrote:

Hello fellow Finkers,

sometime ago I made an updated package for the jack audio connection kit
[1,2]. This was for Jack1. There is also Jack2, which is a
multiprocessor-capable backwards-compatible reimplementation [3]. Having
jack2 packaged is quite important because from my observations jack1
does not work on 10.6.
I believe it would not be possible to package jack2 for fink, as it
installs stuff into /Library/Frameworks and (more importantly) the
Jack.Router into /Library/Audio/Plug-Ins/HAL/. The rest is put into
/usr/local.
Am I right in assuming that it is not feasible to wrap such a program
into a fink package?

Anyway, I thought this would be a good idea to provide a system-jack
package [Attackment] that just looks for the existence of jackd
installed in /usr/local. However, I have got a few questions with this
approach:

- Apparently
Provides: jack, jack-shlibs, jack-dev
  is not sufficient to peacefully co-exist with the exisiting
  Jack1 jack.info. Fink still insists on installing jack1 to satisfy
  a dependency on jack*. Would this be solved by renaming the old
  jack package to e.g. 'jack1*' that also just "Provides" jack* ?

- This approach works well when freshly compiling programs from source,
  but for a binary distribution, wouldn't it be necessary to have two
  versions of each program, one linked against jack and one against
  system-jack? How is this usually handled by other fink packages?

One solution would be to create different versions of each program
depending on jack, like with kde-x11 and kde-mac, but this seems like
unecessary duplication of work. What's best practice in this case?

thanks,
Adrian

[1] http://jackaudio.org/
[2] http://pdb.finkproject.org/pdb/package.php/jack
[3] http://www.jackosx.com/

Good Day Adrian

The latter release of JackOSX seems to be incompatible with coreaudio.
If you excuse the pun) Jack seems to hijack CoreAudio. If JackOSX remains installed and I run `fluidsynth -a
coreaudio...' the jackd server daemon is started and audio is rendered.

The only way I can run fluidsynth with coreaudio is to first remove and trash my Jack installation and then build fluidsynth without Jack.

Just my $0.02.
Ebrahim

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to