[Catalyst-commits] r8885 - trunk/examples/CatalystAdvent/root/2008

Mon Dec 15 17:34:47 GMT 2008

Author: jester
Date: 2008-12-15 17:34:47 +0000 (Mon, 15 Dec 2008)
New Revision: 8885

Modified:
   trunk/examples/CatalystAdvent/root/2008/15.pod
Log:
light editing

Modified: trunk/examples/CatalystAdvent/root/2008/15.pod
===================================================================

--- trunk/examples/CatalystAdvent/root/2008/15.pod	2008-12-15 15:26:02 UTC (rev 8884)
+++ trunk/examples/CatalystAdvent/root/2008/15.pod	2008-12-15 17:34:47 UTC (rev 8885)
@@ -1,6 +1,6 @@
 =head1 Setting up Catalyst environments with C< pkgsrc >
 
-This articl will deal with installing a Catalyst environment with the
+This article will deal with installing a Catalyst environment with the
 NetBSD Package Collection. It will show you how to install an
 environment on a Solaris 9 Sparc box and will briefly show you how
 C< pkgsrc > works.
@@ -10,30 +10,30 @@
 C< pkgsrc > was been introduced in 1997 to the NetBSD project. It's a
 fork of the FreeBSD ports system. C< pkgsrc > for NetBSD follows the
 same goals as the NetBSD project itself which is portability,
-portability and...you know it already. The basic design was heavily
-modified over time and C< pkgsrc > advanced. The first toolchain hack
+portability, and...you know it already. The basic design was heavily
+modified over time and C< pkgsrc > has steadily advanced. The first toolchain hack
 of C< pkgsrc > was made in 1999 in order to support Solaris. In these
 days C< pkgsrc > has become a quite stable package management tool for
-all your third party software needs on all kind of different platforms
-and operating systems.  About 15 operating systems are supported,
-We'll demonstrate it on Solaris 9 sparc.
+all your third-party software needs on all kind of different platforms
+and operating systems.  About 15 operating systems are supported, but
+we'll demonstrate it on Solaris 9/sparc.
 
 =head2 Catalyst on Solaris 9/sparc
 
 In this small example we'll install a Catalyst environment on a
 Solaris 9/sparc server. This machine has a pretty decent support for
-C< pkgsrc > and prebuilt binary packages so getting started with
+C< pkgsrc > and prebuilt binary packages, so getting started with
 Catalyst is quick.  Setting up a basic environment for SUN Solaris
 using C< pkgsrc > is quite easy and isn't very time consuming. Just
-follow the steps described below in order to setup your environment
-for C< pkgsrc > which allows you to install the binary packages for
+follow the steps described below in order to set up your environment
+for C< pkgsrc >, which allows you to install the binary packages for
 Catalyst.
 
 =head2 Bootstrapping C< pkgsrc >
 
 The basic bootstrap kit for C< pkgsrc > contains the necessary tools and a
 small package database. By installing this kit you prepare your SUN
-Solaris server to use C< pkgsrc > with all its capabillities.
+Solaris server to use C< pkgsrc > with all its capabilities.
 
 Just download the kit from:
 
@@ -45,18 +45,17 @@
 C< /usr/pkg > and C< /var/db >.
 
 In order to use the C< pkgsrc > binaries several changes to your
-environment has to be made. C< pkgsrc > uses its own directories for
+environment have to be made. C< pkgsrc > uses its own directories for
 the software which is to be installed. However, Solaris doesn't know
-about the paths which are used by C< pkgsrc > so they need to be added
+about the paths which are used by C< pkgsrc >, so they need to be added
 to the environment. I usually set them in /etc/profile and
-/etc/.login. See the following example how to set up the environment
-for sh/ksh shells (/etc/profile).
+/etc/.login. To set up the environment for sh/ksh shells (/etc/profile):
 
    PATH=/usr/pkg/bin:/usr/pkg/sbin:$PATH
    MANPATH=/usr/pkg/man:$MANPATH
    export PATH MANPATH
 
-If you would like to use a certain server for your binaries make sure
+If you would like to use a different server for your binaries, make sure
 to add the C< PKG_PATH > variable to your favorite package
 location. For sunpkg.de and Solaris 9 on sparc architectures this
 would be:
@@ -65,10 +64,10 @@
            /5.9_2008Q3/All
    export PKG_PATH
 
-just add this to C< /etc/profile >.
+Just add this to C< /etc/profile >.
 
 Before we get started, we need to reload the profile in order to set
-the correct PATH MANPATH PKG_PATH information.
+the correct PATH, MANPATH, and PKG_PATH information.
 
    . /etc/profile
 
@@ -81,8 +80,8 @@
 
  pkg_add p5-Catalyst-Devel
 
-C< pkgsrc > will automatically find the package, downloads it and
-fetches all the dependencies and install them.
+C< pkgsrc > will automatically find the package, download it, and
+fetch all the dependencies and install them.
 
 =head2 Manual installation
 
@@ -92,11 +91,11 @@
 slower Solaris machines.
 
 The advantage to bootstrap manually is to specify the installation
-path. C< pkgsrc > will care for everything automatically so you can
+path. C< pkgsrc > will take care of everything automatically so you can
 have a fully working installation managed by C< pkgsrc > inside your
-home directory. This makes it easy to set up Catalyst at university or
-to ship your webapplication inside a path where the customers want you
-to install.
+home directory. This makes it easy to set up Catalyst in a situation
+where you have limited rights on a system, or to ship your application
+inside a path where the customers want you to install.
 
 =head2 More information
 
@@ -119,7 +118,7 @@
 C<Check for out-of-date packages>
 (L<http://www.pkgbox.org/p2c/>)
 
-Happy installing.
+Happy installing!
 
 Ulrich Habel E<lt>rhaen[at]NetBSD.orgE<gt>
 


