[PR PATCH] Manual.md: relax and clarify the "no sripts" policy

[ahesford <ahesford@users.noreply.github.com>]

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

There is a new pull request by ahesford against master on the void-packages repository

https://github.com/ahesford/void-packages manual
https://github.com/void-linux/void-packages/pull/25707

Manual.md: relax and clarify the "no sripts" policy
I think our "no scripts" policy is too strict and precludes the inclusion of useful administrative tools. These are helpful to have packaged because it makes deploying new Void systems easier by keeping tools in one place. Based on a discussion in #xbps, I propose the following relaxed language that still gives us a reasonable justification for rejecting apparently useless scripts while admitting some more useful ones.

A patch file from https://github.com/void-linux/void-packages/pull/25707.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-manual-25707.patch --]
[-- Type: text/x-diff, Size: 1271 bytes --]

From 622b070a21b9af212ac431988b2222ebf7e6ee6a Mon Sep 17 00:00:00 2001
From: "Andrew J. Hesford" <ajh@sideband.org>
Date: Sun, 18 Oct 2020 10:22:39 -0400
Subject: [PATCH] Manual.md: relax and clarify the "no sripts" policy

---
 Manual.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/Manual.md b/Manual.md
index 4af3a7b78d9..f0a537aeba7 100644
--- a/Manual.md
+++ b/Manual.md
@@ -136,10 +136,11 @@ the Void packages system.
 1. Required: Another package either within the repository or pending inclusion
    requires the package.
 
-In particular, new themes and small shell scripts are highly unlikely
-to be accepted. New fonts are welcome if they provide value beyond
-aesthetics (e.g. they contain glyphs for a script missing in already
-packaged fonts).
+In particular, new themes are highly unlikely to be accepted. Simple shell
+scripts are unlikly to be accepted unless they provide considerable value to a
+broad user base.  New fonts are welcome if they provide value beyond
+aesthetics (e.g. they contain glyphs for a script missing in already packaged
+fonts).
 
 Browser forks, including those based on Chromium and Firefox, are generally not
 accepted. Such forks require heavy patching, maintenance and hours of build time.