os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Clarify some issues about package names.

Browse source
This commit is contained in:
Matthew Hunt 1998-05-07 05:42:39 +00:00
parent a1b1016648
commit b5d9dd20f2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=2782
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
handbook/porting.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: porting.sgml,v 1.95 1998-04-28 04:55:12 mph Exp $ -->
<!-- $Id: porting.sgml,v 1.96 1998-05-07 05:42:39 mph Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
@ -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 `<tt>Data::Dumper</tt>' 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').
<item>If the port can be built with different hardcoded
defaults (usually specified as environment variables or on