Re: LilyPond v2.20.0 on Raspberry Pi OS (Debian buster)

[wferi]

renyhp <renyhp@disroot.org> writes:

> If the path of installing debs is totally closed, is it possible to
> make my own build?

Ask the Debian package maintainer to provide an official backport.  It
should be straightforward.  Actually I tried to build the lilypond
source package on buster (amd64 architecture) and it failed at a very
late step, during making the install-WWW target:

/usr/bin/make --no-builtin-rules out=www install-WWW
make[3]: Entering directory '/<<PKGBUILDDIR>>'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
/<<PKGBUILDDIR>>/scripts/build/out/install -c -m 755 -d 
/<<PKGBUILDDIR>>/debian/tmp/usr//share/doc/lilypond/html
rsync -rl --exclude='*.signature' ./out-www/offline-root/ 
/<<PKGBUILDDIR>>/debian/tmp/usr//share/doc/lilypond/html
rsync: change_dir "/<<PKGBUILDDIR>>//./out-www/offline-root" failed: No such 
file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 
23) at main.c(1207) [sender=3.1.3]

This dummy.dep thing is some quirk or the Lilypond build system which I
don't get, but somebody knowledgeable could probably pinpoint the issue
causing the dummy build in no time.
-- 
Regards,
Feri