Fix dependencies #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This pull request fixes the dependencies in `info.rkt`, as the `rchess` package has some dependencies it either doesn't declare or inaccurately declares as build dependencies. The most common reasons this happens are: - This package uses code from a dependency of a dependency, implicitly relying on the fact that the undeclared dependency will be installed in the process of installing the direct dependency. This means this package will break if the direct dependency stops depending on the undeclared dependency. - This package declares a `build-dep` dependency but that dependency is used in regular code, rather than only in test submodules or Scribble docs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes the dependencies in
info.rkt, as therchesspackage has some dependencies it either doesn't declare or inaccurately declares as build dependencies. The most common reasons this happens are:build-depdependency but that dependency is used in regular code, rather than only in test submodules or Scribble docs.