[pkgsrc/trunk]: pkgsrc/doc/portability-book/files Wrote a short introduction.

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/d22744fa1b4f
branches:  trunk
changeset: 520187:d22744fa1b4f
user:      rillig <rillig%pkgsrc.org@localhost>
date:      Tue Oct 17 06:41:01 2006 +0000

description:
Wrote a short introduction.

diffstat:

 doc/portability-book/files/intro.xml |  18 ++++++++++++++++--
 1 files changed, 16 insertions(+), 2 deletions(-)

diffs (28 lines):

diff -r 2e6088428525 -r d22744fa1b4f doc/portability-book/files/intro.xml
--- a/doc/portability-book/files/intro.xml      Tue Oct 17 06:28:33 2006 +0000
+++ b/doc/portability-book/files/intro.xml      Tue Oct 17 06:41:01 2006 +0000
@@ -1,8 +1,22 @@
-<!-- $NetBSD: intro.xml,v 1.1.1.1 2006/10/06 21:10:41 rillig Exp $ -->
+<!-- $NetBSD: intro.xml,v 1.2 2006/10/17 06:41:01 rillig Exp $ -->
 
 <chapter id="intro">
 <title>Introduction</title>
 
-<para>Blubb.</para>
+<para>Writing programs that are portable to a wide range of platforms
+isn't easy. Maybe some platforms are lacking your favorite tool, while
+others implemented it, but with arbitrary limitations. Some don't have
+such useful functions like <funcname>snprintf</funcname> or
+<funcname>strlcpy</function>.</para>
+
+<para>This book provides information about which features are
+<emphasis>not</emphasis> on the platforms, since the features that
+<emphasis>are</emphasis> available are already documented quite well. It
+also explains how portable shell programs look like, since that's also a
+topic that hasn't spread wide yet.</para>
+
+<para>Since pkgsrc uses the POSIX tools quite a lot, and the packages
+using all other features, it's good to know on which platforms a certain
+program will not work without further work.</para>
 
 </chapter>