[pkgsrc/trunk]: pkgsrc/doc/guide/files Cut long line and refill paragraph.

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/213295df2e7e
branches:  trunk
changeset: 495148:213295df2e7e
user:      jmmv <jmmv%pkgsrc.org@localhost>
date:      Fri Jun 03 13:05:20 2005 +0000

description:
Cut long line and refill paragraph.

diffstat:

 doc/guide/files/pkginstall.xml |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (22 lines):

diff -r 105e2e2756a3 -r 213295df2e7e doc/guide/files/pkginstall.xml
--- a/doc/guide/files/pkginstall.xml    Fri Jun 03 12:54:11 2005 +0000
+++ b/doc/guide/files/pkginstall.xml    Fri Jun 03 13:05:20 2005 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: pkginstall.xml,v 1.2 2005/06/03 12:54:11 wiz Exp $ -->
+<!-- $NetBSD: pkginstall.xml,v 1.3 2005/06/03 13:05:20 jmmv Exp $ -->
 
 <chapter id="pkginstall"> <?dbhtml filename="pkginstall.html"?>
 <title>The pkginstall framework</title>
@@ -284,9 +284,9 @@
 <para>As said before, pkginstall automatically handles configuration files.
 This means that <emphasis role="strong">the packages themselves must not
 touch the contents of <filename>${PKG_SYSCONFDIR}</filename>
-directly</emphasis>.  Bad news is that many software installation scripts will, out of
-the box, mess with the contents of that directory.  So what is the correct
-procedure to fix this issue?</para>
+directly</emphasis>.  Bad news is that many software installation scripts
+will, out of the box, mess with the contents of that directory.  So what is
+the correct procedure to fix this issue?</para>
 
 <para>You must teach the package (usually by manually patching it) to
 install any configuration files under the examples hierarchy,