Add error that explains PackageSpec.repo is a private field #4170
Conversation
This file contains hidden or 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
IanButterworth
force-pushed
the
ib/packagespec_repo_private
branch
2 times, most recently
from
9dd17fb to
33f955a
Compare
IanButterworth
force-pushed
the
ib/packagespec_repo_private
branch
from
33f955a to
5c1e800
Compare
IanButterworth
commented
Feb 25, 2025
|
@KristofferC what do you think? This or should we use it if set? Silently ignoring it is confusing. |
IanButterworth
commented
Jul 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
See JuliaPackaging/BinaryBuilderBase.jl#416 (comment)
Alternatively we could just use the
repoentry if it's already populated? But it's not in the docs currently https://pkgdocs.julialang.org/v1/api/#Pkg.PackageSpec