musescore: update to 4.6.5

[chrysos349]

I made changes so that musescore could find the packages below:

• migrated flac, libogg, libsndfile to cmake
• added lame.pc to lame not allowed, thus removed
• replaced libflac with flac as a dep in libflac-devel, because /usr/lib64/cmake/FLAC/targets.cmake requires binaries.

Testing the changes

• I tested the changes in this PR: YES

Local build testing

• I built this PR locally for my native architecture, (x86-64)

[Rutpiv]

While looking into a MuseScore update, I noticed this PR also switches flac, libogg, and libsndfile to CMake. I’m not opposed to the change, but I might be missing some context: what’s the rationale?

According to upstream documentation, all three projects still support both autotools and CMake. In particular, libogg and libsndfile describe autotools as the primary or recommended build system, while FLAC treats both as equivalent.

For reference, I built MuseScore 4.6.4 locally against the current packages, without these build-system changes, and the build completed successfully. The only thing I noticed was CMake warnings about missing package config files for FLAC and libsndfile (SndFile) (e.g. FLACConfig.cmake / SndFileConfig.cmake), and then it fell back to pkg-config and continued.

I also tested the resulting build locally, and everything is working perfectly on my side. Thanks for working on this update.

Given that, is the goal mainly to provide CMake package config files/targets for these libraries and eliminate those warnings, or is there a concrete MuseScore-related failure with the autotools-built variants?

[chrysos349]

Bundled deps vs system deps