OpenPKG CVS Repository
http://www.openpkg.org/cvsweb/cvsweb.cgi
____________________________________________________________________________
Server: cvs.openpkg.org Name: Michael Schloh
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-doc Date: 09-Jul-2002 17:05:33
Branch: HEAD Handle: 2002070916053200
Modified files:
openpkg-doc/handbook openpkg.xml
Log:
Add text defining platform requirements and update version numbers throughout.
Clarify section on unofficial support.
Summary:
Revision Changes Path
1.45 +60 -30 openpkg-doc/handbook/openpkg.xml
____________________________________________________________________________
Index: openpkg-doc/handbook/openpkg.xml
============================================================
$ cvs diff -u -r1.44 -r1.45 openpkg.xml
--- openpkg-doc/handbook/openpkg.xml 9 Jul 2002 15:03:43 -0000 1.44
+++ openpkg-doc/handbook/openpkg.xml 9 Jul 2002 15:05:32 -0000 1.45
@@ -867,12 +867,12 @@
<itemizedlist>
<listitem>
<simpara>
- FreeBSD 4.[1234], Debian GNU/Linux 2.2, Sun Solaris 2.[678]
+ FreeBSD 4.[123456], Debian GNU/Linux 2.2, Sun Solaris 2.[6789]
</simpara>
</listitem>
<listitem>
<simpara>
- cc, make, ar, ld, as, nm, ... in $PATH
+ Software (see <xref linkend='bstrap-sfware'/>)
</simpara>
</listitem>
<listitem>
@@ -882,7 +882,12 @@
</listitem>
<listitem>
<simpara>
- /dev/[u]random
+ /dev/random
+ </simpara>
+ </listitem>
+ <listitem>
+ <simpara>
+ /dev/urandom
</simpara>
</listitem>
</itemizedlist>
@@ -890,22 +895,29 @@
As a practicality, the current OpenPKG has been implemented to run on
three of the most commonly found Internet server platforms<footnote>
<para>Precisely, the officially supported operating system version
- numbers are Sun Solaris 2.[678], Debian GNU/Linux 2.2, and FreeBSD
- 4.[1234].</para></footnote>. Sun Solaris (SPARC), Linux, and FreeBSD
- fully support all functionality of OpenPKG and have native packages
- built to order on OpenPKG servers supplying packages to the official
-<!-- <footnote><para></para></footnote>-->
- OpenPKG ftp server <ulink
+ numbers are Sun Solaris 2.[6789], Debian GNU/Linux 2.2, and FreeBSD
+ 4.[123456].</para></footnote>. Sun Solaris (SPARC), Linux (iX86), and
+ FreeBSD (iX86) fully support all functionality of OpenPKG and have
+ native packages built to order on OpenPKG servers supplying packages
+ to the official OpenPKG ftp server <ulink
url='ftp://ftp.openpkg.org'>ftp://ftp.openpkg.org</ulink> and web site
<ulink url='http://www.openpkg.org'>OpenPKG</ulink>. Additionally,
- NetBSD, OpenBSD, and Compaq Tru64 are unofficially supported with
- partial functionality. This means that to use OpenPKG, the
- administrator is limited to these platforms. This is true whether
- OpenPKG is installed from source or binary. However, the good news is
+ RedHat Linux (iX86), Solaris (iX86), NetBSD (SPARC and iX86), OpenBSD
+ (iX86), and Compaq Tru64 (Alpha) operating systems are unofficially
+ supported. In most cases, these target platforms succeeded in
+ bootstrapping and later package installations. They remain with only
+ unofficial support however, because they are not in enough day-to-day
+ use during OpenPKG testing to guarantee complete functionality on a
+ regular basis.
+ </para>
+ <para>
+ The platform requirements of OpenPKG are independent of its use, and
+ so the inherent operating system constraint exists regardless of
+ installation of source or binary packages. However, the good news is
that no real limitation exists for how or where OpenPKG can work.
Developers have ported the OpenPKG source code from its original
FreeBSD roots to other platforms, and it should indeed be easy to port
- to any Unix brand of operating system.
+ to any Unix brand of operating system.
</para>
</sect1>
@@ -924,7 +936,8 @@
<para>
There are also tools which OpenPKG doesn't bundle but requires
nevertheless. Missing any of these important tools will either
- cause an OpenPKG installation to fail abruptly, or maybe more subtly.
+ cause an OpenPKG installation to fail abruptly, or maybe more subtly
+ later on.
<itemizedlist>
<listitem>
<simpara>
@@ -953,12 +966,27 @@
</listitem>
<listitem>
<simpara>
- /dev/random
+ cc (compiler)
</simpara>
</listitem>
<listitem>
<simpara>
- /dev/urandom
+ ar (archiver)
+ </simpara>
+ </listitem>
+ <listitem>
+ <simpara>
+ ld (linker)
+ </simpara>
+ </listitem>
+ <listitem>
+ <simpara>
+ as (assembler)
+ </simpara>
+ </listitem>
+ <listitem>
+ <simpara>
+ nm (name symbol viewer)
</simpara>
</listitem>
</itemizedlist>
@@ -975,8 +1003,11 @@
There exist some exceptions to these requirements. Installation of
OpenPKG on Debian Linux will fail unless GNU gettext and libpam0g-dev
are installed. Also, to later build packages like jdk-sun, the library
- compat-libstdc++ must exist.
-<!--FIXME: Describe RedHat, Solaris 9, and FreeBSD particular requirements-->
+ compat-libstdc++ must exist. Particular caution goes to Solaris users
+ who may find a cc command on a freshly installed system to be nothing
+ more than a useless wrapper script.
+ </para>
+<!--FIXME: Describe Solaris 9 and FreeBSD exact requirements-->
</sect1>
<sect1 id='bstrap-multi'>
@@ -1261,17 +1292,16 @@
to match the programming language of the application's source. The
common problems with assembler or linker versions also do not exist.
An OpenPKG source package is easy to recognize. Its file name ends
- with 'src.rpm'. A binary package does not have this identifying
- file name postfix. Though binary packages also end with '.rpm', the
- name preceding '.rpm' will match the operating system that the
- package was compiled for. As an example, either package
- bison-1.29-1.src.rpm or bison-1.29-1.ix86-freebsd4.4-cw.rpm can be
- downloaded and installed on a computer running FreeBSD 4.4 with the
- same end result. In either case of source or binary package
- installation, the administrator issues the same commands to install
- packages. In fact, with OpenPKG an administrator doesn't need to
- know the nature or contents of a package at all in order to
- successfully install it.
+ with 'src.rpm'. A binary package does not have this identifying file
+ name postfix. Though binary packages also end with '.rpm', the name
+ preceding '.rpm' will match the operating system that the package
+ was compiled for. As an example, either package bison-1.29-1.src.rpm
+ or bison-1.29-1.ix86-freebsd4.6-cw.rpm can be downloaded and
+ installed on a computer running FreeBSD with the same end result. In
+ either case of source or binary package installation, the
+ administrator issues the same commands to install packages. In fact,
+ with OpenPKG an administrator doesn't need to know the nature or
+ contents of a package at all in order to successfully install it.
</para>
</sect2>
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
