Repository navigation
Default to ghostscript-agpl over ghostscript-gpl #68
Description
Activity
I've switched trunk over to ghostscript-agpl and it will be the default in 2018Q1 onwards.
- added a commit that references this issue
on Feb 19, 2018 - added 2 commits that reference this issue
on Mar 14, 2018 - added a commit that references this issue
on Mar 31, 2018 - added a commit that references this issue
on Mar 26, 2019 - added 2 commits that reference this issue
on Aug 26, 2019 134 remaining items
- added 8 commits that reference this issue
on May 14, 2026 - added 2 commits that reference this issue
on May 22, 2026 - added a commit that references this issue
on Jul 13, 2026 - added a commit that references this issue
on Aug 26, 2026 - added a commit that references this issue
on Sep 9, 2026 - added 2 commits that reference this issue
on Sep 24, 2026
Metadata
Metadata
Assignees
Labels
No labels
Currently when a package links against or depends on ghostscript it defaults to ghostscript-gpl.
This is an old version with open security issues. It appears as though ghostscript changed licensing from gpl to agpl and the gpl package is an old snapshot pre the change.
Given that the package is effectively now unsupported it would make sense to change to the ghostscript-agpl package to be the default which is kept current with upstream.