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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why?
virtual?java-runtime
will accept any package that providesjava-runtime
virtual dependency, this includes bothopenjdk17-jre
and the current distro-wide default ofopenjdk8-jre
.If you install
openjdk17-jre
you should be able to removeopenjdk8-jre
, or why not keep both. You could also installopenjdk17-jre
beforePolyMC
and thenopenjdk8-jre
won't be pulled in.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah nvm attempting to install
PolyMC
pulls inopenjdk11-jre
by default for me onx86_64-musl
, wonder what exactly makes that the case... Either way this is a bit of a nuanced issue, perhaps @classabbyamp can comment better.I previously suggested mentioning the existance of PolyMC's README.voidlinux but it seems that was completely lost in the comments, but the file should already exist as
/usr/share/doc/PolyMC/README.voidlinux
on your system.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair, but README or not, this still means that the package wouldn't have accurate dependencies which puts into question the point of deps in the first place. Not to mention the extra work for new users who'll have to switch one version out for another.