From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: PolyMC: Update Java runtime dependencies
Date: Sat, 13 Aug 2022 18:48:15 +0200 [thread overview]
Message-ID: <20220813164815.cA_gEBEwhe1Dk2ysXtXf1_CXxl3bER3lc1JJgYyeN5Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38648@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/38648#issuecomment-1214188332
Comment:
Void policy is to only include the *absolutely required* software in dependencies, not optional software. PolyMC can work with any of the three openjdk runtimes we currently package, so that requirement is put in the depends.
PolyMC provides a nice, clear error message if it doesn't have the correct jdk *and* README.voidlinux (which is [the standard way](https://docs.voidlinux.org/config/package-documentation/index.html) to let users know about void-specific documentation with a package) says the same thing.
Forcing the dependency to `openjdk17-jre` would cause errors if a user only wanted to have other versions of openjdk on their system:
```
xbps-install PolyMC
...
xbps-remove openjdk17-jre
openjdk17-jre-17.0.3+7_1 in transaction breaks installed pkg `PolyMC-1.4.1_2'
```
This is not good.
`virtual?openjdk-runtime` is the correct dependency for PolyMC.
next prev parent reply other threads:[~2022-08-13 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 12:11 [PR PATCH] " TrueTechie
2022-08-13 12:17 ` [PR REVIEW] " JamiKettunen
2022-08-13 12:19 ` JamiKettunen
2022-08-13 12:27 ` JamiKettunen
2022-08-13 13:51 ` paper42
2022-08-13 14:31 ` [PR REVIEW] " JamiKettunen
2022-08-13 15:37 ` TrueTechie
2022-08-13 15:39 ` TrueTechie
2022-08-13 16:48 ` classabbyamp [this message]
2022-08-13 16:55 ` [PR PATCH] [Closed]: " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220813164815.cA_gEBEwhe1Dk2ysXtXf1_CXxl3bER3lc1JJgYyeN5Y@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).