-
Notifications
You must be signed in to change notification settings - Fork 273
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
Safe and Simple #959
Comments
It occurs to me that you might be waiting for me to cut releases of some of these packages. If so, I apologize for the delay. Should I interpret a "TODO" in the table as "this is awaiting a new Hackage release", and that I should make such a release after you have made a corresponding PR to that repo? |
TODO are just things to do in general. At this point, I think And |
OK. If there's no hurry, then I'll default to waiting until someone explicitly asks for a new release. Thanks again for picking this up! |
Well... if we sort |
My next request is for releases of
Which are needed for |
safe and simple free. Maybe someone could come up with some pun. As mentioned on IRC I'll continue work on (FWIW, making |
As outlined elsewhere, I'm going to traverse kmettverse to make it
build-type: Simple
. As I'm on it, I'll also try to make it explicitly Safe (or Trustworthy). This issue is too track the progress.Dependency tree
For now I target only what is below
free
:build-type: Simple
means removing the dependency oncabal-doctest
(and yellow boxes -setup
components).Tasks
Packages in reverse topological order
Status
2020-12-31
The text was updated successfully, but these errors were encountered: