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

Mon Dec 15 09:47:37 GMT 2008

Author: zarquon
Date: 2008-12-15 09:47:37 +0000 (Mon, 15 Dec 2008)
New Revision: 8882

Added:
   trunk/examples/CatalystAdvent/root/2008/15.pod
Log:
day 15

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

--- trunk/examples/CatalystAdvent/root/2008/15.pod	                        (rev 0)
+++ trunk/examples/CatalystAdvent/root/2008/15.pod	2008-12-15 09:47:37 UTC (rev 8882)
@@ -0,0 +1,126 @@
+=head1 Setting up Catalyst environments with C< pkgsrc >
+
+This articl 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.
+
+=head2 Introduction
+
+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
+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.
+
+=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
+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
+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.
+
+Just download the kit from:
+
+ ftp://ftp.netbsd.org/pub/pkgsrc/packages/SunOS/sparc/5.9_2008Q3/\
+ bootstrap-pkgsrc-SunOS-5.9-sparc-2008Q3.tar.gz
+
+Gunzip and untar this package as the root user to the root directory
+of your system. It will leave you with a small everything installed to
+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
+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
+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).
+
+   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
+to add the C< PKG_PATH > variable to your favorite package
+location. For sunpkg.de and Solaris 9 on sparc architectures this
+would be:
+
+   PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/SunOS/sparc\
+           /5.9_2008Q3/All
+   export PKG_PATH
+
+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.
+
+   . /etc/profile
+
+The installation of the C< pkgsrc > bootstrap kit is now finished.
+
+=head1 Installation of Catalyst
+
+The basic installation of the Catalyst package is quite simple. Just
+type:
+
+ pkg_add p5-Catalyst-Devel
+
+C< pkgsrc > will automatically find the package, downloads it and
+fetches all the dependencies and install them.
+
+=head2 Manual installation
+
+The bootstrap proccess can be run manually to choose different
+installation paths. Please refer to the manual to get started. The
+advantage of using the prebuilt binaries is to save lots of time on
+slower Solaris machines.
+
+The advantage to bootstrap manually is to specify the installation
+path. C< pkgsrc > will care for 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.
+
+=head2 More information
+
+The NetBSD community tries very hard to keep everything
+up-to-date. However, C< pkgsrc > uses 3 month release cycles which
+leave packages a bit behind. If you want to test out the latest stuff,
+make sure to use the -current branch of C< pkgsrc >.
+
+Here are some links which helps you to keep everything working:
+
+C<The NetBSD Packages Collection>
+(L<http://www.pkgsrc.org>)
+
+C<The NetBSD pkgsrc guide>
+(L<http://www.netbsd.org/docs/pkgsrc/index.html>)
+
+C<A nice webinterface to pkgsrc>
+(L<http://www.pkgsrc.se>)
+
+C<Check for out-of-date packages>
+(L<http://www.pkgbox.org/p2c/>)
+
+Happy installing.
+
+Ulrich Habel E<lt>rhaen[at]NetBSD.orgE<gt>
+
+=cut


