eli found that the musecore build system recognizes a -DBUILD_WEBENGINE=OFF cmake define

What do we have to write in the command-line so the source is compiled without the WebEngine, considering that cmake define you mentioned?

normally you would pass the defines to the `cmake` command, just as i wrote it, which generates a makefile to be compiled later with the `make` command - the typical cmake procedure within a PKGBUILD looks like this:

$ mkdir build
$ cd build
$ cmake -DCMAKE_BUILD_TYPE=Release  \
        -DCMAKE_INSTALL_PREFIX=/usr \
        -DCMAKE_INSTALL_LIBDIR=lib  ..
$ make

so normally, one would simply add to that command: -DBUILD_WEBENGINE=OFF - but this package is quite peculiar in that the makefile is already present in the sources, and the `cmake` command is embedded within the makefile; and the PKGBUILD uses `sed` to change the default defines

anyways i have compiled it for x86_64 and i686 - they should appear in the repos within a few hours - there was a problem with ARM though, so i will leave this ticket open for now

just for documentation purposes, another peculiar quirk of this program is that the static makefile expects the source tree to be under git; and although the upstream does publish tarballs; the upstream tarballs fail to build, because the 'release' makefile target depends on a running a git command on the sources to get the version number

compiling from git however, results in source-balls weighing in at nearly 700MB each (one per arch); where the binary package itself is a mere 32MB (re: https://labs.parabola.nu/issues/2403#note-10)

Hey bill-auger, I've realized now that you marked the status as fixed, so forgive me for not responding earlier. Thank you for bringing this app libre'd for the community, man, it's running fine on my desktop. I upgraded my system with pacman -Syu, then proceeded to install musescore. Works as intended, great job.

yw - do you know what musescore uses webengine for? - like what functionality is missing without it - it is often just the help browser

I don't remember it having a help documentation depending on webengine, but I remember it using web services if you wanted to upload your music scores to https://musescore.com/ I think that's basically the only feature that will be missing that I, however, won't be missing. You always have the option to use your browser if you want to upload your music scores, so that's no biggie.

The latest version (4.0-2) no longer depends on qt5-webengine, so libre/musescore can be deprecated and musescore can be removed from the blacklist. However, the latest Arch PKGBUILD has some other issues: it downloads a copy of the code using a git tag instead of a sourceball and it is missing checksums.

From a quick glance, there are also many modules and features we probably don't want or need.
https://github.com/musescore/MuseScore/blob/master/CMakeLists.txt
The "cloud" module is probably useless to us, the "plugin" module is probably a TPPM that connects to a TPR, the "update" module is probably not needed because Parabola uses native packages, the "diagnostics" module is probably not needed, the "crashpad" module is probably not private because it uses Google services, "download soundfont" uses the network at build-time, the "network" module is probably only needed for those various undesirable modules, "precompiled headers" does not build from source, we don't need unit tests, and we probably want to use system freetype.