Skip to content

chore: relicense to GPL-3.0-or-later - #4

Merged
MotherSphere merged 1 commit into
mainfrom
chore/relicense-gpl-3.0-or-later
Aug 1, 2026
Merged

chore: relicense to GPL-3.0-or-later#4
MotherSphere merged 1 commit into
mainfrom
chore/relicense-gpl-3.0-or-later

Conversation

@MotherSphere

Copy link
Copy Markdown
Member

Eidos was consistently GPL-3.0-only. Nothing here was contradictory; this
broadens the grant so downstreams may redistribute under version 3 or any
later GPL the FSF publishes, and so the copyleft dependencies Eidos already
links (libloot, GPL-3.0-or-later) compose without a version ceiling.

The LICENSE file is deliberately untouched: the verbatim FSF GPL-3.0 text is
identical for -only and -or-later. The distinction lives entirely in the SPDX
strings and the prose, which is what changed:

  • Cargo.toml - the workspace license key. All 17 member crates take it via
    license.workspace = true and none overrides it, so this single line is the
    whole Rust-metadata change.
  • packaging/PKGBUILD - license=(), the SPDX id pacman records. The
    install -Dm644 LICENSE line is unaffected, the shipped text is unchanged.
  • README.md - the License section said a bare "GPL-3.0", which reads as -only
    to anyone applying the SPDX default.
  • assets/brand/README.md - same bare "GPL-3.0" on the grant covering the logo
    and icon artwork, which is first-party original work.
  • crates/eidos-gamefeatures/assets/PROVENANCE.md - names Eidos's own licence
    when flagging how it interacts with the bundled Microsoft DirectX
    redistributables. Only that reference moved; the surrounding statement that
    those DLLs are governed by the Microsoft Windows SDK terms is untouched.

Third-party material was left exactly as found, since it is not ours to
relicense: the MO2 toolbar icons under crates/eidos-gui/assets/icons (GPL-3.0,
ModOrganizer2/modorganizer, attributed in main.rs), the upstream MO2 plugins
vendored under reference/ (GPL-3.0, the Mod Organizer 2 Team), and the
Microsoft DirectX redistributable DLLs described in PROVENANCE.md.

Eidos was consistently GPL-3.0-only. Nothing here was contradictory; this
broadens the grant so downstreams may redistribute under version 3 or any
later GPL the FSF publishes, and so the copyleft dependencies Eidos already
links (libloot, GPL-3.0-or-later) compose without a version ceiling.

The LICENSE file is deliberately untouched: the verbatim FSF GPL-3.0 text is
identical for -only and -or-later. The distinction lives entirely in the SPDX
strings and the prose, which is what changed:

* Cargo.toml - the workspace `license` key. All 17 member crates take it via
  `license.workspace = true` and none overrides it, so this single line is the
  whole Rust-metadata change.
* packaging/PKGBUILD - `license=()`, the SPDX id pacman records. The
  `install -Dm644 LICENSE` line is unaffected, the shipped text is unchanged.
* README.md - the License section said a bare "GPL-3.0", which reads as -only
  to anyone applying the SPDX default.
* assets/brand/README.md - same bare "GPL-3.0" on the grant covering the logo
  and icon artwork, which is first-party original work.
* crates/eidos-gamefeatures/assets/PROVENANCE.md - names Eidos's own licence
  when flagging how it interacts with the bundled Microsoft DirectX
  redistributables. Only that reference moved; the surrounding statement that
  those DLLs are governed by the Microsoft Windows SDK terms is untouched.

Third-party material was left exactly as found, since it is not ours to
relicense: the MO2 toolbar icons under crates/eidos-gui/assets/icons (GPL-3.0,
ModOrganizer2/modorganizer, attributed in main.rs), the upstream MO2 plugins
vendored under reference/ (GPL-3.0, the Mod Organizer 2 Team), and the
Microsoft DirectX redistributable DLLs described in PROVENANCE.md.
@MotherSphere
MotherSphere merged commit 05890c8 into main Aug 1, 2026
5 of 6 checks passed
@MotherSphere
MotherSphere deleted the chore/relicense-gpl-3.0-or-later branch August 1, 2026 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant