Github messages for voidlinux
 help / color / mirror / Atom feed
From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: PolyMC-1.1.0
Date: Fri, 25 Mar 2022 15:08:01 +0100	[thread overview]
Message-ID: <20220325140801.ww_exyPmwzo9hcsfp5rywmDPxzzlKOER-yRcAavysr4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34979@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

New comment by JamiKettunen on void-packages repository

https://github.com/void-linux/void-packages/pull/34979#issuecomment-1079054056

Comment:
This should probably print a similar message to steam if there's an  README.voidlinux, I don't think looking for a `README.voidlinux` in output of `xbps-query -f` (or `/usr/share/doc/$pkgname` for that matter) is the first thing users would do if something doesn't work or am I wrong?
```
steam-1.0.0.74_2: post-install message:
========================================================================
Consult /usr/share/doc/steam/README.voidlinux for further installation
instructions and troubleshooting information.
========================================================================
steam-1.0.0.74_2: installed successfully.
```
At some point `java-runtime` and `java-environment` should probably be bumped to JDK 17 since it is the latest LTS release after all, so then installing an older JDK may only be necessary for older MC versions.

  parent reply	other threads:[~2022-03-25 14:08 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 12:06 [PR PATCH] New package: PolyMC-1.0.5 oynqr
2022-01-10 12:19 ` [PR PATCH] [Updated] " oynqr
2022-01-21 19:32 ` sug0
2022-01-22  9:28 ` oynqr
2022-01-31 10:27 ` [PR PATCH] [Updated] " oynqr
2022-01-31 12:13 ` New package: PolyMC-1.0.6 oynqr
2022-02-16 16:09 ` Scrumplex
2022-02-17 15:54 ` [PR PATCH] [Updated] " oynqr
2022-02-17 15:55 ` oynqr
2022-02-18  3:46 ` [PR REVIEW] " ericonr
2022-02-18  3:46 ` ericonr
2022-02-18  9:23 ` [PR PATCH] [Updated] " oynqr
2022-02-18  9:26 ` [PR REVIEW] " oynqr
2022-02-18  9:26 ` oynqr
2022-02-21  0:32 ` classabbyamp
2022-02-21  9:17 ` [PR PATCH] [Updated] " oynqr
2022-02-22 11:37 ` oynqr
2022-02-22 11:47 ` oynqr
2022-02-25 12:34 ` JamiKettunen
2022-02-25 12:55 ` JamiKettunen
2022-02-25 12:55 ` [PR REVIEW] " JamiKettunen
2022-02-25 12:55 ` JamiKettunen
2022-02-25 12:59 ` JamiKettunen
2022-02-25 15:06 ` classabbyamp
2022-02-25 19:47 ` JamiKettunen
2022-02-26  9:34 ` oynqr
2022-02-26  9:36 ` Scrumplex
2022-02-26  9:39 ` oynqr
2022-02-26  9:40 ` [PR PATCH] [Updated] " oynqr
2022-02-26  9:43 ` [PR REVIEW] " oynqr
2022-02-26 14:34 ` classabbyamp
2022-02-26 15:56 ` oynqr
2022-03-12 16:44 ` [PR PATCH] [Updated] " oynqr
2022-03-13 17:18 ` [PR PATCH] [Updated] New package: PolyMC-1.1.0 oynqr
2022-03-13 17:30 ` oynqr
2022-03-13 19:08 ` [PR REVIEW] " Johnnynator
2022-03-13 21:34 ` oynqr
2022-03-14  8:38 ` [PR PATCH] [Updated] " oynqr
2022-03-14  9:19 ` oynqr
2022-03-14  9:51 ` [PR REVIEW] " paper42
2022-03-14 20:04 ` oynqr
2022-03-14 20:13 ` paper42
2022-03-14 21:45 ` oynqr
2022-03-14 22:36 ` classabbyamp
2022-03-15  6:46 ` oynqr
2022-03-15  6:49 ` [PR PATCH] [Updated] " oynqr
2022-03-15 16:16 ` [PR REVIEW] " DioEgizio
2022-03-15 17:06 ` oynqr
2022-03-15 17:40 ` sug0
2022-03-15 17:41 ` DioEgizio
2022-03-15 22:40 ` [PR REVIEW] " paper42
2022-03-16  7:53 ` oynqr
2022-03-16  7:55 ` paper42
2022-03-16  7:59 ` oynqr
2022-03-16  8:09 ` [PR REVIEW] " oynqr
2022-03-16  9:32 ` [PR PATCH] [Updated] " oynqr
2022-03-16 13:01 ` classabbyamp
2022-03-16 15:53 ` [PR PATCH] [Updated] " oynqr
2022-03-16 16:17 ` [PR REVIEW] " DioEgizio
2022-03-20 20:18 ` [PR PATCH] [Updated] " oynqr
2022-03-24 16:04 ` DioEgizio
2022-03-25  1:24 ` [PR REVIEW] " tibequadorian
2022-03-25 14:08 ` JamiKettunen [this message]
2022-03-25 14:24 ` tibequadorian
2022-03-25 14:45 ` tibequadorian
2022-04-01 20:27 ` [PR PATCH] [Updated] " oynqr
2022-04-03 16:05 ` New package: PolyMC-1.1.1 DioEgizio
2022-04-04 14:07 ` [PR PATCH] [Updated] " oynqr
2022-04-04 17:59 ` oynqr
2022-04-04 18:09 ` [PR REVIEW] " classabbyamp
2022-04-04 18:47 ` Scrumplex
2022-04-04 20:21 ` oynqr
2022-04-04 21:41 ` classabbyamp
2022-04-05  0:07 ` tibequadorian
2022-04-05  7:50 ` oynqr
2022-04-08 16:30 ` Uiyx
2022-04-08 18:17 ` DioEgizio
2022-04-08 21:23 ` [PR PATCH] [Merged]: " Johnnynator

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=20220325140801.ww_exyPmwzo9hcsfp5rywmDPxzzlKOER-yRcAavysr4@z \
    --to=jamikettunen@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).