I couldn't complete all my depencies.
Some of them dont exist under names from ubuntu or even at all.
Although I was able to run liquidsoap and icecast2 without any problems. And I know that airtime is heavily based on savonet engine.
Now I wonder do I need all of those depencies ?
Mostly I couldn't find all those ocaml stuff but my liquidsoap is running fine so I must have at least few of them.
I couldn't find also daemontools-run,python-configobj, poc-streamer,python-mutagen and libportaudio2
neither in ports or packages. These must be probably under different names i think.
Maybe someone created port or binary package and already solved those problems ?
Not as far as we know. The only officially supported server platform for
Airtime is GNU/Linux, and at the moment development is mostly taking
place on Ubuntu 10.04 LTS. You'll make a lot less work for yourself if
you install that distro on your server.
> I couldn't complete all my depencies.
> Some of them dont exist on under names from ubuntu or even at all.
I'm not surprised about that, FreeBSD is a different platform. It may be
a cousin of GNU/Linux, but it's far from 100% compatible.
> Maybe someone created port or binary package and already solved those
> problems ?
I don't think Sourcefabric would encourage that, it would just lead to
additional support variables which would significantly increase the cost
of development and QA. Please consider that Sourcefabric is a non-profit
organisation, so it has to allocate resources very carefully.
Hi levi, fortunatly, there is another way to run airtime on freebsd as far as I could guess, the only thing prevents you from having it up&running - "pyinotify" (linux only) if you succeed in "porting" py-scripts from "inotify" to "kqueue" (freebsd native) - e.g. by watchdog package ..., you'll have it done, if I'm not mistaken of course. Other dependencies seem to be resolvable even on freebsd (in my case - freebsd 7.2 release, airtime 1.9.5) + fix paths/environment variables/etc in scripts, replace liquidsoap's binary by one compiled from source etc. Good luck.
Update: Well, I've had it up and running on FreeBSD (7.2-RELEASE, airtime-1.9.5) at last. Via ports -> devel/libinotify pyinotify -> compile from source (replace the next string in setup.py and pyinotify.py: from libc_name = ctypes.util.find_library('c') to libc_name = ctypes.util.find_library('inotify') to use the freebsd's libinotify instead of linux'es libc) in order not to rewrite py-scripts from pyinotify to kqueue everytime after airtime upgrade