From b5d9dd20f265abcefbf78330afb15fb11780b575 Mon Sep 17 00:00:00 2001 From: Matthew Hunt Date: Thu, 7 May 1998 05:42:39 +0000 Subject: [PATCH] Clarify some issues about package names. --- handbook/porting.sgml | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/handbook/porting.sgml b/handbook/porting.sgml index d46156a1b9..eb621a722d 100644 --- a/handbook/porting.sgml +++ b/handbook/porting.sgml @@ -1,4 +1,4 @@ - + Porting an existing piece of free software @@ -1718,9 +1718,15 @@ msql:*:80:249:mSQL-2 pseudo-user:/var/db/msqldb:/bin/sh programs in it). Things like XFree86 (yes there really is a package of it, check it out) and ImageMagick fall into this category. Otherwise, convert the name (or at least the - first letter) to lowercase. If the software in question - really is called that way, you can have numbers, hyphens and - underscores in the name too (like `kinput2'). + first letter) to lowercase. If the capital letters are + important to the name (for example, with one-letter names + like R or V) you may use capital letters at your discretion. + There is a tradition of naming Perl 5 modules by prepending + `p5-' and converting the double-colon separator to a hyphen; + for example, the `Data::Dumper' module becomes + `p5-Data-Dumper'. If the software in question has numbers, + hyphens, or underscores in its name, you may include them as + well (like `kinput2'). If the port can be built with different hardcoded defaults (usually specified as environment variables or on