These fixes all sound desirable to me. Can the Powers that Be give Nedko access to commit ebuilds to the pro-audio overlay? He writes half the audio apps anyway :P
On Mon, Oct 11, 2010 at 8:59 PM, Nedko Arnaudov <[email protected]> wrote: >> Revision: 1765 >> Author: gentoid >> Date: 2010-10-10 17:47:55 +0200 (Sun, 10 Oct 2010) >> Log Message: >> ----------- >> jack_mixer: bump to 9 & git-version >> >> Modified Paths: >> -------------- >> trunk/overlays/proaudio/media-sound/jack_mixer/ChangeLog >> trunk/overlays/proaudio/media-sound/jack_mixer/Manifest >> trunk/overlays/proaudio/media-sound/jack_mixer/jack_mixer-8.ebuild >> >> Added Paths: >> ----------- >> trunk/overlays/proaudio/media-sound/jack_mixer/jack_mixer-9.ebuild >> trunk/overlays/proaudio/media-sound/jack_mixer/jack_mixer-9999.ebuild > > 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. > > -- > Nedko Arnaudov <GnuPG KeyID: DE1716B0> >
