> binary directly from that path. Moving it isn't recommended as liquidsoap
> also uses other resources located under the same prefix.

ok, thx, that's what I thought.
how do I actually see what kind of support I have in liquidsoap?
does liquidsoap --conf-dump only show what's compiled in? 

> Also, the liquidsoap-daemon opam package should let you setup a running
> daemon for liquidsoap quite easily.

well, sort of. can't fullfil all dependecies easily on a debian7... i.e.
there are quite some packages simply not available. 

struggeling at the moment to do a simple opam install fdkaac ... 
no libfdk-aac-dev on debian7...

thx, u.




> > I've just installed liquidsoap 1.2 with opam on a debian oldstable
> > (need to use with that for a while...)
> > worked surprisingly smooth, no errors, nice. I'm not familiar with opam
> > though.
> > How am I supposed to run liquidsoap now? Does it need the opam
> > environment (in ~/.opam) or can i move the binary somewhere in the
> > PATH? Sorry if that topic was covered already... but need a hint.
> >
> > thanks, udo


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to