Contributed 3rd Party Builds • Re: AppImage of Pale Moon available

How is section 3b to be understood?

as (a)

Did that AppImage file bundle GPL binaries?

No idea; they didn't tell me. But I assume it's being bundled with dependent system libs to make it portable and self-contained. If I assume wrong, then maybe I need to make it more specific.

Were they GPL binaries that Pale Moon does not bundle, or is it that Pale Moon does not bundle anything?

Pale Moon does not bundle GPL licensed code. It bundles some LGPL licensed libs in a format allowing them to be easily changed out, which satisfies the bundling license exception.

Does "incorporating" mean bundling in this case, and never "packaging together"?

AppImages, Snaps and flatpaks are constructed in such a way that they become (monolithic) executable packages. This means by definition you cannot untangle any bundled (as in packaged together in the monolithic file) libs from the rest of the application and it is therefore becoming an extended version of what any GPL lib inside it supplies, meaning it has to be relicensed under the GPL, which is not compatible with the MPL (which is file-granular). The GPL is really bad in that respect, trying to absorb and enforce itself on anything that becomes hard-reliant on a GPL licensed program.