-
Notifications
You must be signed in to change notification settings - Fork 184
GAP should not require PrimgGrp/SmallGrp/TransGrp packages #2434
Copy link
Copy link
Open
Labels
kind: discussiondiscussions, questions, requests for comments, and so ondiscussions, questions, requests for comments, and so onkind: enhancementLabel for issues suggesting enhancements; and for pull requests implementing enhancementsLabel for issues suggesting enhancements; and for pull requests implementing enhancementstopic: packagesissues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)issues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)
Metadata
Metadata
Assignees
Labels
kind: discussiondiscussions, questions, requests for comments, and so ondiscussions, questions, requests for comments, and so onkind: enhancementLabel for issues suggesting enhancements; and for pull requests implementing enhancementsLabel for issues suggesting enhancements; and for pull requests implementing enhancementstopic: packagesissues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)issues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)
Type
Fields
Give feedbackNo fields configured for issues without a type.
The libraries of small, primitive and transitive groups which previously were an integral part of GAP were split into three separate packages:
For backwards compatibility, these are required packages in GAP 4.9 (i.e., GAP will not start without them). We plan to change this for GAP 4.10, once all packages which currently implicitly rely on these new packages had time to add explicit dependencies on them.
This issue under the milestone 4.10 is created to track this: