-
Notifications
You must be signed in to change notification settings - Fork 8
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
Dealing with (and debugging) package installation errors #66
Labels
feature request
New feature
Comments
Perhaps there could be an option |
See #119 for a first draft on this |
I've renamed the option to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unfortunately it seems difficult to debug issues when installing a package using PackageManager fails, esp. packages that have compiled code. The reason for that is that the failed package is deleted, and with it all debug logs etc. For example, from gap-packages/NormalizInterface#96:
So... it seems it even compiled, but then failed to load. Replicating the problem can be difficult; in this case, I believe the package actually compiled correctly, but then there was an issue caused by the setting of the GAPROOTs. But I am not 100% sure, and since manually building the package worked, I have a hard time reproducing it.
So it would be nice if there was some facilities to help with that. E.g. an option to tell the PackageManager to not delete the package that was just compiled. Perhaps also some other things could be done, I am happy to discuss.
The text was updated successfully, but these errors were encountered: