OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Michael Schloh
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-doc Date: 14-Jan-2004 12:02:05
Branch: HEAD Handle: 2004011411020400
Modified files:
openpkg-doc/handbook 00TODO openpkg.xml
Log:
Remember change of directory name for binary packages, and edit random
device requirements text
Summary:
Revision Changes Path
1.34 +25 -0 openpkg-doc/handbook/00TODO
1.80 +11 -10 openpkg-doc/handbook/openpkg.xml
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-doc/handbook/00TODO
============================================================================
$ cvs diff -u -r1.33 -r1.34 00TODO
--- openpkg-doc/handbook/00TODO 14 Jan 2004 09:19:43 -0000 1.33
+++ openpkg-doc/handbook/00TODO 14 Jan 2004 11:02:04 -0000 1.34
@@ -419,3 +419,28 @@
o Sun Solaris 9
tbd
+
+--
+
+Binary Package Releases
+
+ OpenPKG binary packages are made available for each supported platform.
+ These packages should in principle be ignored, as one of the pillars of
+ OpenPKG integrity suggests building from source in every case. However,
+ exceptions exist (see section blah...) in which a binary package is
+ needed.
+
+Change in Released Binary Package Naming Scheme
+
+ Previous to version 2.0, binary (release grade) packages were released.
+ These packages will install to the '/cw' directory (see explanation cool
+ world...). From version 2.0 on, binary packages are released but will
+ install to a different directory '/openpkg'.
+
+ This is meaningless to the admin who never uses binary packages according
+ to OpenPKG recommendation. For those installing binary packages from
+ OpenPKG version 2.0 and later, attention should be given to this change.
+ For example, scripts installing OpenPKG 2.0 binary packages and later
+ expecting the resulting software to be available in '/cw' will now fail.
+
+
@@ .
patch -p0 <<'@@ .'
Index: openpkg-doc/handbook/openpkg.xml
============================================================================
$ cvs diff -u -r1.79 -r1.80 openpkg.xml
--- openpkg-doc/handbook/openpkg.xml 26 Aug 2003 08:30:45 -0000 1.79
+++ openpkg-doc/handbook/openpkg.xml 14 Jan 2004 11:02:04 -0000 1.80
@@ -33,7 +33,7 @@
</author>
</authorgroup>
- <pubdate>July 2003</pubdate>
+ <pubdate>January 2004</pubdate>
<abstract>
<para>
@@ -1222,17 +1222,18 @@
in question.
</para>
</sect2>
- <sect2 id='support-random'>
- <title>Support for /dev/random respectively /dev/urandom</title>
+ <sect2 id='bstrap-random'>
+ <title>Device Requirements /dev/random and /dev/urandom</title>
<para>
- By default, Solaris 8 does neither /dev/random nor /dev/urandom which
- is mandatory for proper operations of certain packages like OpenSSH or
- BIND 9. In the meantime Sun provided an official patch to add the
- missing functionality to Solaris 8. The patch can be downloaded at
+ Most Solaris 8 installations do not have the pseudorandom number
+ devices /dev/random and /dev/urandom. These devices are mandatory
+ for several OpenPKG packages such as OpenSSH and BIND 9. To correct
+ this, Sun provides an official patch for Solaris 8 which installs the
+ missing devices. The patch can be downloaded at
<ulink url='ftp://sunsolve.sun.com/pub/patches/112438-02.zip'>
- ftp://sunsolve.sun.com/pub/patches/112438-02.zip</ulink>. Please take a
- look at the <ulink url='ftp://sunsolve.sun.com/pub/patches/112438.readme'>
- patch description file</ulink> first for further details.
+ ftp://sunsolve.sun.com/pub/patches/112438-02.zip</ulink>. Read the
+ <ulink url='ftp://sunsolve.sun.com/pub/patches/112438.readme'>
+ patch description file</ulink> for more information.
</para>
</sect2>
</sect1>
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
