From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: clean up INSTALL.msgs
Date: Wed, 06 Sep 2023 00:29:20 +0200 [thread overview]
Message-ID: <20230905222920.JCnpsD6tnBQPa15SgadlkyhTN6OZQVHy4X0Ayq3OhZ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44273@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
There's a merged pull request on the void-packages repository
clean up INSTALL.msgs
https://github.com/void-linux/void-packages/pull/44273
Description:
This PR aims to reduce the number of unnecessary messages that users see at every install and update, so that they can focus on the important ones.
After this change, there are only 19 packages with `INSTALL.msg`, down from 146.
Most `INSTALL.msg`s were simply lists of optional dependencies or package-specific documentation, and were moved to `README.voidlinux`. Some others were indicators that a package had been removed (instead of using `removed-packages`) or was a bootstrap package (message removed, users will never see it with the bootstrap repo).
I intentionally did not revbump any packages except for `removed-packages` because I am unsure if all of these packages currently build.
#### Testing the changes
- I tested the changes in this PR: **briefly**
[ci skip]
prev parent reply other threads:[~2023-09-05 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 8:12 [PR PATCH] " classabbyamp
2023-06-05 8:14 ` [PR PATCH] [Updated] " classabbyamp
2023-07-28 4:44 ` classabbyamp
2023-09-05 22:26 ` classabbyamp
2023-09-05 22:29 ` classabbyamp [this message]
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=20230905222920.JCnpsD6tnBQPa15SgadlkyhTN6OZQVHy4X0Ayq3OhZ8@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).