Research other SVG libs as an alternative to librsvg and make a test implementation
Edit by Jehan on 2020-05-04:
Getting rid of SVG support, one of the major image format in graphics nowadays, doesn't seem the most reasonable thing to do. But if librsvg is really a problem for compatibility on more architectures, we may study other dependencies.
(apparently libresvg is also Rust, so not available on enough archs) is a possible candidate (and actually the main dev of
librsvg advised us to look at it one day, if not mistaken). It would be worth look at it, test it, and implement our SVG support with it to see if:
either we could just drop librsvg support if we find another SVG lib just as good.
or keep both implementations as build-time alternatives, allowing packagers on less supported archs to switch to a supported dependency.
INSTALL docs still suggest that
./configure --without-rsvg can be used to disable support for SVG, but this was removed back in 2016: https://bugzilla.gnome.org/show_bug.cgi?id=773382
Rather than to fix the docs, I would rather beg you to bring back the option. Librsvg upstream has gone rogue, rewriting the entire library in rust and dropping security support for the older rust-free versions. In practice this means that there is no secure way to use librsvg. The old versions have known vulnerabilities, and the new versions statically link a few gigabytes of rust code onto your machine that will never receive any security updates (I normally enjoy irony). Moreover, rust is not cross-platform, so as long as GIMP has a hard dependency on librsvg, GIMP isn't cross-platform either. This affects our GIMP packages in Gentoo where, for example, we are forced to use the old insecure versions of librsvg on the "unusual" arches we support.