From: Singustromo <Singustromo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: radio-sh-2.0
Date: Thu, 19 Jan 2023 14:01:33 +0100 [thread overview]
Message-ID: <20230119130133.wlTGbyseMyhIOB81a9qBujIXV0dahg1BtU37-1EXITs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41737@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
New comment by Singustromo on void-packages repository
https://github.com/void-linux/void-packages/pull/41737#issuecomment-1396940319
Comment:
> > 1. System: The software should be installed system-wide, not per-user.
> > 2. Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system.
> > 3. Required: Another package either within the repository or pending inclusion requires the package.
> >
> > [...] Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base. [...]
>
> from [CONTRIBUTING.md](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements)
>
> how does this meet those requirements?
All right, I thought it might be something worth adding since there are also packages like #14199 with a similar functionality but also with more dependencies. I don't really think this is a **small** unneeded script.
next prev parent reply other threads:[~2023-01-19 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 4:13 [PR PATCH] " Singustromo
2023-01-19 4:22 ` classabbyamp
2023-01-19 4:58 ` ahesford
2023-01-19 4:58 ` [PR PATCH] [Closed]: " ahesford
2023-01-19 13:01 ` Singustromo [this message]
2023-01-19 13:12 ` Singustromo
2023-01-19 13:13 ` Singustromo
2023-01-19 13:20 ` ahesford
2023-01-19 15:31 ` Singustromo
2023-01-19 15:32 ` Singustromo
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=20230119130133.wlTGbyseMyhIOB81a9qBujIXV0dahg1BtU37-1EXITs@z \
--to=singustromo@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).