Skip to content
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 incorrect package structure warnings. #1236

Merged
merged 5 commits into from
Jul 7, 2024

Conversation

planetis-m
Copy link
Contributor

@planetis-m planetis-m commented Jul 6, 2024

As discussed https://forum.nim-lang.org/t/11942 and probably in more places before. This PR removes all checks for package structure, these are two but they seem closely tied, regardless everything should work fine even without the warnings.

@@ -176,10 +117,6 @@ proc validatePackageInfo(pkgInfo: PackageInfo, options: Options) =
if pkgInfo.backend notin ["c", "cc", "objc", "cpp", "js"]:
raise validationError("'" & pkgInfo.backend &
"' is an invalid backend.", false)
if options.action.typ in {actionInstall, actionBuild, actionDevelop, actionCompile, actionCheck}:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively we can limit the warning to show for only actionCheck, actionDevelop.

Warning: Symlink already exists in /home/runner/work/nimble/nimble/tests/nimbleDir/bin/y. Replacing.
@planetis-m
Copy link
Contributor Author

Fails at installing different Nim versions tniminstall.nim seems unrelated.

@jmgomez
Copy link
Collaborator

jmgomez commented Jul 7, 2024

Fails at installing different Nim versions tniminstall.nim seems unrelated.

tniminstall.nim doesnt fail. What fails is [FAILED] can validate package structure (#144) in tissues.nim

@Araq Araq merged commit 31dcee5 into nim-lang:master Jul 7, 2024
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants