-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove primgrp, smallgrp, transgrp from required packages #2589
Conversation
@fingolfin thanks - just to let you know I've seen this and will run extended tests of PR using my parametrised Jenkins build - I'm specifying the number of the PR, and then id does the same as in The changes are obviously correct, it's the impact of them that we need to estimate and report to authors of affected packages. |
Observed problems are of different kinds:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think one of the first modifications of this PR would be to add these three packages to the set of packages loaded by default:
Line 1751 in 42789e6
default:= [ "autpgrp", "alnuth", "crisp", "ctbllib", "factint", "fga", |
@fingolfin one of the first modifications of this PR would be to add these three packages to the set of packages loaded by default - could you please update the PR? |
@fingolfin ping? |
This way, at least in principle one can load GAP without them.
c08ab92
to
c910ee4
Compare
Codecov Report
@@ Coverage Diff @@
## master #2589 +/- ##
=========================================
Coverage ? 43.35%
=========================================
Files ? 111
Lines ? 57739
Branches ? 0
=========================================
Hits ? 25033
Misses ? 32706
Partials ? 0 |
Updated as requested |
Dismissing review to create another review request
The number of diffs is still overwhelming. I would prefer to deal with this one by one. Either there should be three separate PRs, or you can try now to remove only PrimGrp and see what happens. The majority of diffs are coming from SmallGrp, and we need to discuss how to deal with that. |
To be honest, I am not sure it's worth the bother, so I don't intend to do anything about this PR. It really was meant more as a reminder; for now I think there are far more important issues to think about. |
Fine, so the summary is that many problems show up, they are classified as below, and we need to discuss how to deal with them and in which priority.
The complexity for untangling this for each package may be different. |
This PR has no chance to be merged anytime soon, if ever, and at the same time is trivial, so I don't see a point in keeping this open. |
This starts work on issue #2434. Let's see what breaks, if anything.
Though we may not see any breakage without dedicated tests, at least in packages...