| Re: [proaudio] jack_mixer, phat, lash and ladish |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] jack_mixer, phat, lash and ladish
- From: Viktor Lazarev <taurus101v@xxxxxxxxx>
- Date: Fri, 15 Oct 2010 21:08:06 +0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=E6a/Vq1lD3n0pxtwd/BAZvxcvvvC8TiNyiIR4l8eCJo=; b=fpoMuBKoblX1FpZXGnUqRJKGNZKCoMZOSW2UhDMnX96IhX/YmMa294qqJ2Kb1eVk2z 4U+yCOI7WfBLxHwvpG/fOYTh0Xu4hlrU9extypo+dVgaIbCY6O4V6Ga0pnQtLLFEnFQd 4uh4YSU0K2l8OCVrSMVdas7XfUGf71Cj0W9nw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=S+qix/TYmL7D+CMAkqF9w5K2UChEnvZ+b+N3QgBnbT7swXwEeyT//qLe/XUvoP7veE 7Gg4UTFD7dLzHOQ2Tcdtlm9aGAo0ZEkbeuvDlEmMn6dfu3hlTG1xis+a64FKDoDAVsDk qHm3VLZC2H3IDeOU0mrYtQ6wmW/s9Hv/Ipm1c=
2010/10/11, Nedko Arnaudov <nedko@xxxxxxxxxxxxx>:
> These ebuilds are not quite right. They specify lash and pyphat as
> required build time dependencies. They are optional runtime
> dependencies.
>
> I've patched them in my git branch:
>
> http://nedko.arnaudov.name/git/cgit.cgi/proaudio-overlay/commit/?h=nedko&id=91d3ceb0cd77c996255d992c7bf8a6715728f415
>
> A patch that should apply cleanlyy against svn can be downloaded from
> this url:
>
> http://nedko.arnaudov.name/git/cgit.cgi/proaudio-overlay/patch/?id=91d3ceb0cd77c996255d992c7bf8a6715728f415
>
> In the ladi-overlay [1] I've changed lash and ladish to provide a virtual
> liblash package. I've made this in order to build dino against liblash
> From ladish.
>
> [1] http://repo.or.cz/w/ladi-overlay.git
>
> If you are interested, I can prepare a changeset that will make all apps
> in the proaudio overlay to depend on virtual/liblash instead of lash.
>
> The patch for jack_mixer does not make jack_mixer to depend on
> virtual/liblash. I dont use jack_mixer`s lash support because ladish L1
> support (since version 9) is enough for me.
>
> The case with pylash is complicated though. I see that jack_mixer
> depends on pylash or lash[python]. pylash should be usable with liblash
> From ladish but I never tried it. What is the better approach, to depend
> on lash[python] or pylash? I can make ladish to provide python bindings
> for liblash, if you think that "|| (lash[python] ladish[pylash])" is
> better than separate pylash package.
In point of fact, I don't know what is the better. I have no exp with
using lash/ladish/pylash.
>
> --
> Nedko Arnaudov <GnuPG KeyID: DE1716B0>
>
--
WBR, Viktor