Re: [NEW] audio/zynaddsubfx

On Sun, Mar 21, 2021 at 11:46:48AM +0000, Stuart Henderson wrote:
> On 2021/03/21 11:30, Solene Rapenne wrote:
> > On Thu, 18 Mar 2021 17:36:55 +0000
> > Dimitri Karamazov <deserter666@danwin1210.me>:
> >
> > > Ping
> > >
> >
> > hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
> > it seems mandatory to use zyn-fusion.
>
> The problem is that the dependency is sort-of circular. zynaddsubfx
> requires zyn-fusion or another UI to be useful, and zyn-fusion requires
> zynaddsubfx to be useful.
>
> AUR deals with this by including zynaddsubfx in zyn-fusion (and having
> them conflict) but that doesn't seem ideal either.
>
> Thinking about what happens if other UIs are added though, having
> zynaddsubfx depend on zyn-fusion doesn't work because the user might want
> a different UI.
>
> Maybe the answer is to have zyn-fusion depend on zynaddsubfx and move
> the README to zynaddsubfx ("this package provides the backenx synthesizer,
> you must also install a user interface") - or even just including it in
> DESCR.
>
> The other way is to use meta-packages but that's messier ..

There is a configure option -DGuiModule in zynaddsubfx which can be set to
zest(zyn-fusion), ntk or fltk. So making zyn-fusion depend on zynaddsubfx
will not work(restrict our options to zest). Also zyn-fusion has no real
dependency on zynaddsubfx it is not needed during build or runtime. It
is a hollow ui and is supposed to be so.

zyn-fusion(zest) is a runtime dependency, while on the other hand fltk
and ntk are linked with zynaddsubfx. Only one of these frontends can be
installed at a time.

Since files created vary with the value of GuiModule, I will have to use
MULTI_PACKAGES, and then set dependencies and CONFIGURE_ARGS for each
subpackage(like fltk,ntk and zyn-fusion). I see no other possibility to
allow Gui choices but to make zynaddsubfx depend on zyn-fusion, then add
other frontends with MULTI_PACKAGES.
>
> > When I run zynaddsubfx or zyn-fusion, I see no difference, is it
> > normal? Both open a X window with a keyboard at the bottom of the
> > window. If both binaries could be used for the same result, I would
> > remove the README file and just add a RUN_DEP.

The result should not be same. Check the images I've attached.
`zyn-fusion` - image1.png

This interface has no connection with the backend and hence is utterly
useless.

`zynaddsubfx` - image2.png

Shows all intruments and knobs are connected with the backend.
Hope it is the same for you.
> >
> > zynaddsubfx has some -O3 in the build log, this is something that must
> > be fixed before we can import it.
> >
> > zynaddsubfx HOMEPAGE can be swiched to https
> >

Fixed.