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

IANAL but IIUC, section 4 of the LGPLv3, or section 6 in LGPLv2.1 only ensures that your terms do not prohibit the user from effectively modifying the LGPL'd library. In the older 2.1 version it's even clearer that "the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications". Our redist license doesn't really prevent the user from modifying Pale Moon for personal use, so there shouldn't be an issue with control over branding being lost. It restricts the user from redistributing the modified version (which is effectively what happens if you switch the bundled GTK for another one in a repack) under the Pale Moon name without permission, but the LGPL doesn't care about that. The free software philosophy is also fine with requiring a change to the name of the program when you release a modified version of it:

Rules about how to package a modified version are acceptable, if they don't substantively limit your freedom to release modified versions, or your freedom to make and use modified versions privately. Thus, it is acceptable for the license to require that you change the name of the modified version, remove a logo, or identify your modifications as yours. As long as these requirements are not so burdensome that they effectively hamper you from releasing your changes, they are acceptable; you're already making other changes to the program, so you won't have trouble making a few more.