[pkgsrc/trunk]: pkgsrc/doc/guide/files guide: Recommend that PKGNAME be lower...

[nia <nia%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/3a6580f22bdc
branches:  trunk
changeset: 454683:3a6580f22bdc
user:      nia <nia%pkgsrc.org@localhost>
date:      Mon Jun 14 22:53:02 2021 +0000

description:
guide: Recommend that PKGNAME be lowercase

diffstat:

 doc/guide/files/components.xml |  9 +++++++--
 1 files changed, 7 insertions(+), 2 deletions(-)

diffs (23 lines):

diff -r 909ce74afbc4 -r 3a6580f22bdc doc/guide/files/components.xml
--- a/doc/guide/files/components.xml    Mon Jun 14 22:41:19 2021 +0000
+++ b/doc/guide/files/components.xml    Mon Jun 14 22:53:02 2021 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: components.xml,v 1.60 2021/03/26 17:43:20 gdt Exp $ -->
+<!-- $NetBSD: components.xml,v 1.61 2021/06/14 22:53:02 nia Exp $ -->
 
 <chapter id="components"> <?dbhtml filename="components.html"?>
 <title>Package components - files, directories and contents</title>
@@ -38,7 +38,12 @@
     regular expression
     <varname>^[A-Za-z0-9][A-Za-z0-9-_.+]*$</varname>, that is, it
     starts with a letter or digit, and contains only letters, digits,
-    dashes, underscores, dots and plus signs.</para></listitem>
+    dashes, underscores, dots and plus signs.
+    New packages should have entirely lower-case names, with the exception
+    of some that must follow pre-existing conventions
+    (e.g. R packages begin with <varname>R-</varname>).
+    You can use the <code>:tl</code> variable modifier to lower-case
+    the package name.</para></listitem>
 
     <listitem><para><varname>CATEGORIES</varname> is a list of categories
     which the package fits in. You can choose any of the top-level