MuseScore (and soundfonts) backporting plans

[Thorsten Glaser]

On Thu, 5 Apr 2018, Fabian Greffrath wrote:

> Have you considered to trigger a transition in backports from
> fluidr3mono-gm-soundfont to musescore-general-soundfont by turning the
> former into a dummy package with a dependency on the latter?

No, first and foremost because we don't do this in sid/testing,
but also because fluidr3mono isn't going to go away.

While musescore-general is a fork off it, fluidr3mono will
still have its use cases, especially as the former is expected
to kinda explode in size, so users of systems with less RAM
will need to use the latter.

I was more thinking of "we don't really need to backport this"
but turns out we do, but it's not a problem (more of a consideration
of mirror space and laziness). But thanks anyway.

Anyway, fluidr3mono is now in backports-NEW too.

bye,
//mirabilos
-- 
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font.	-- Rob Pike in "Notes on Programming in C"