Am Montag, den 06.07.2015, 15:00 +0000 schrieb Jack Underwood:
> It has?  As far as I see musescore-2.0.1+dfsg-2 still has
> musescore-soundfont-gm as a dependency, with fluid-soundfont-gm and
> timgm6mb-soundfont as Suggests... (if things have changed please
> disregard) this means that musescore2 still depends on timgm6mb-soundfont
> via musescore-soundfont-gm despite it listed as a Suggests.

Oh, indeed, this appears to be an oversight.

> Personally I vote for taking this font out and putting it its own package
> like the other fonts.  As far as I understand FluidR3Mono_GM just represents
> a lighter version of the already packaged fluid-soundfont-gm, which means it
> works better on slower computers.  By turning this into a virtual package,

Nope. The new soundfont is in SF3 format which means that it contains
OGG-compressed samples and is currently incompatible with anything else
but musescore itself. As soon as other sound renderers, e.g.
fluidsynth, gain ability to use this sound font format, I agree, it
should get split into its own separate package and be made available to
these other sound renderes as well.

> and keeping it as a required package for musescore we effectively allow the
> user to pick and choose whether they want to just install the lite or the full
> version of this font (of course they can still install both, but this would
> give the user that extra option).

Not sure why you refer to "virtual packages", but we have simple
alternative dependencies for that. However, I think musescore should
well depend on its own sound font, but merely suggest the other
available ones.

> Anyway, just an idea, I don't know what plans you have for the package.  Just
> really wanting to give MuseScore 2 a spin :).

I don't have any plans, I just read the pkg-multimedia mailing list. ;)

Cheers,

Fabian

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to