lilypond: update to 2.21.7

[newbluemoon]

(obsolete: Tested 2.21.2 on x86_64, x86_64-musl, i686 and armv7l.)
Tested 2.21.3 on x86_64-musl.

[newbluemoon]

I’ll work on using the new system-texlive instead of texlive-bin for the next update which should simplify the template a bit and should prevent those 'tlmgr not found' errors. In the meantime this should be good as is.

[newbluemoon]

Modified the template to use system texlive now. Tested on x86_64-musl, armv7l-musl, built for i686 (not tested, yet). No problems encountered so far.

However, to build it needs t1utils which is disabled in the texlive template. So I made it an extra package, but I’m not sure if it should be provided by texlive as texlive-bin does? @fosslinux is there a reason you omitted it?

[fosslinux]

Not off the top of my head. I will try to enable it. It should probably be distributed with TeXLive.

[q66]

why does lilypond need texlive at all?

[newbluemoon]

@q66 For once it takes the tex-gyre fonts, translates them with t1asm and packages them.

[q66]

can't we somehow separate that so that it doesn't need to install texlive to build?

[q66]

as far as i can tell, we can, it doesn't seem to need the texlive distribution, just the font and the util

[newbluemoon]

It also needs texlive for creating the docs, but since we ship the pre-built ones anyway it doesn’t matter.
And it isn’t really a runtime-dependency, only optional. So I’m going to drop the INSTALL.msg.

Regarding the fonts I think listing them as distfiles and pointing configure to them might be easiest. I’ll try to see how it works out.

We have to keep t1utils as a separate package then, but other distributions (debian, ubuntu, arch) have it separately, too.

[newbluemoon]

It needs MetaFont and MetaPost. So texlive is still required.

[newbluemoon]

2.21.5 tested on x86_64-musl.

Any suggestion on how to proceed further? Keep t1utils as a separate package (as e.g. Debian has it) or provide it by texlive?