OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 25-Feb-2004 10:26:00
Branch: HEAD Handle: 2004022509255901
Added files:
openpkg-web bootstrap.gif
Modified files:
openpkg-web releng.wml security.wml tutorial.wml
Log:
flush pending updates for OpenPKG 2.0
Summary:
Revision Changes Path
1.1 BLOB openpkg-web/bootstrap.gif
1.11 +5 -5 openpkg-web/releng.wml
1.79 +10 -2 openpkg-web/security.wml
1.23 +249 -164 openpkg-web/tutorial.wml
____________________________________________________________________________
(cd openpkg-web && \
uudecode <<'@@ .' && \
xdelta patch bootstrap.gif.xdelta /dev/null bootstrap.gif && \
rm -f bootstrap.gif.xdelta)
Index: openpkg-web/bootstrap.gif
============================================================================
begin 664 bootstrap.gif.xdelta
M)5A$6C`P-"4````(`!$`$`````````````````````!S:&EE;&$N,S$Y-3,N
M;G5L;'-H:65L82XS,3DU,RYA;&[EMAIL PROTECTED]"```
M``````-C8&[EMAIL PROTECTED]@,[EMAIL PROTECTED]&SAEO?CC5`<[EMAIL PROTECTED]<````````
)52581%HP,#0E
`
end
@@ .
patch -p0 <<'@@ .'
Index: openpkg-web/releng.wml
============================================================================
$ cvs diff -u -r1.10 -r1.11 releng.wml
--- openpkg-web/releng.wml 7 Aug 2003 14:46:09 -0000 1.10
+++ openpkg-web/releng.wml 25 Feb 2004 09:26:00 -0000 1.11
@@ -11,13 +11,13 @@
The class of a source package can be determined by running:
<pre>
-$ rpm -qp --qf '%{DISTRIBUTION}' <i>foo-1.2-3.4.src.rpm</i>
+$ openpkg rpm -qp --qf '%{CLASS}' <i>foo-1.42-2.0.0.src.rpm</i>
</pre>
The class of an installed package can be determined by running:
<pre>
-$ rpm -q --qf '%{DISTRIBUTION}' <i>foo</i>
+$ openpkg rpm -q --qf '%{CLASS}' <i>foo</i>
</pre>
The classes are differentiated by multiple attributes as
@@ -37,7 +37,7 @@
<table cellspacing=0 cellpadding=1 border=0 bgcolor="#a5a095"><tr><td>
<table cellspacing=1 cellpadding=1 border=0 bgcolor="#e5e0d5">
- <tr><td> </td> <ab RTT> <ab SAP> <ab OPS> <ab RSS> <ab RBP>
<ab RSP> <ab BLD> <ab PKG> </tr>
+ <tr><td> </td> <ab RTT> <ab SAP> <ab FPS> <ab RSS> <ab RBP>
<ab RSP> <ab BLD> <ab PKG> </tr>
<tr bgcolor="#f5f0e5"><td>CORE</td> <yes> <yes> <yes> <yes> <yes>
<yes> <yes> <yes> </tr>
<tr bgcolor="#d5d0c5"><td>BASE</td> <no> <yes> <yes> <yes> <yes>
<yes> <yes> <yes> </tr>
<tr bgcolor="#f5f0e5"><td>PLUS</td> <no> <no> <no> <no> <no>
<yes> <yes> <yes> </tr>
@@ -53,10 +53,10 @@
</tr>
<tr><td>RTT: </td><td>Run-Time Tested</td></tr>
<tr><td>SAP: </td><td>Security Advisories and Patches</td></tr>
- <tr><td>OPS: </td><td>Official Platform Support Build Requirement</td></tr>
+ <tr><td>FPS: </td><td>Full Platform Support Build Requirement</td></tr>
<tr><td>RSS: </td><td>Release Show-Stopper</td></tr>
- <tr><td>RSP: </td><td>Release Source Package</td></tr>
<tr><td>RBP: </td><td>Release Binary Package</td></tr>
+ <tr><td>RSP: </td><td>Release Source Package</td></tr>
<tr><td>BLD: </td><td>Building Successful on all Supported
Platforms</td></tr>
<tr><td>PKG: </td><td>Packaging Completed</td></tr>
</table>
@@ .
patch -p0 <<'@@ .'
Index: openpkg-web/security.wml
============================================================================
$ cvs diff -u -r1.78 -r1.79 security.wml
--- openpkg-web/security.wml 16 Jan 2004 12:43:44 -0000 1.78
+++ openpkg-web/security.wml 25 Feb 2004 09:26:00 -0000 1.79
@@ -43,8 +43,8 @@
released for CORE and BASE class packages of:
<ul>
+ <li>OpenPKG 2.0
<li>OpenPKG 1.3
- <li>OpenPKG 1.2
</ul>
Older releases are not maintained and users are strongly encouraged to upgrade
@@ -164,11 +164,19 @@
In order to verify the digital signatures, follow these steps:
<ol>
+<li><b>OpenPKG 2.0</b>
+ <p>
+ OpenPKG 2.0 has the capability to check signed packages with built-in
+ cryptographic tools. The OpenPKG OpenPGP public key is preinstalled and
+ appears as if it were a package. OpenPGP is only necessary to verify
+ things different from packages, i.e. an advisory text, or to sign
+ packages.
+<p>
<li><b>Install GnuPG</b>
<p>
This is the preferred tool for working with OpenPGP. We recommend you to
install it by using the OpenPKG <a
- href="ftp://ftp.openpkg.org/release/1.3/SRC/gnupg-1.2.2-1.3.0.src.rpm";>
+ href="ftp://ftp.openpkg.org/release/1.3/SRC/gnupg-1.2.2-1.3.1.src.rpm";>
gnupg</a> package.
Alternatively you can fetch it from its official homepage <a
href="http://www.gnupg.org/";>http://www.gnupg.org/</a> and build/install
@@ .
patch -p0 <<'@@ .'
Index: openpkg-web/tutorial.wml
============================================================================
$ cvs diff -u -r1.22 -r1.23 tutorial.wml
--- openpkg-web/tutorial.wml 23 Feb 2004 17:37:34 -0000 1.22
+++ openpkg-web/tutorial.wml 25 Feb 2004 09:26:00 -0000 1.23
@@ -1,141 +1,181 @@
#use "page.inc" page=tutorial
-<define-tag release>1.3</define-tag>
+<define-tag release>2.0</define-tag>
<define-tag bashver>2.05b</define-tag>
<title>User Tutorial</title>
<h1>User Tutorial</h1>
+This tutorial guides you on your way into the world of OpenPKG. It
+explains some essential cornerstones, shows you how to bootstrap OpenPKG
+and shows you how to use OpenPKG to install a common and useful example
+application, GNU bash.
+
+<h2>Cornerstones</h2>
+
+<h3>Platform Support</h3>
+By design minimal assumptions about the underlying Unix flavor are made.
+Nevertheless it is quixotic to assume every operating system receives
+equal support. Some platforms are fully supported, some are supported
+and the remainder might work.
+
+<h3>Package Types</h3>
+Two types of packages exist, source and binary. A source package usually
+contains all files necessary to build a binary package. This includes the
+pristine vendor sources, patches, fake syslog library configuration and
+run commands. It also contains a <tt>spec</tt>
+file which is the heart of OpenPKG. Inside are instructions how to
+unpack, modify, patch, build, install and otherwise transform into a
+installable binary package. The source package can be thought of being
+a clonogenic cell which adapts to the target machine and a arbitrary
+prefix when being transformed into a binary package. A source package
+might have options which will further augment the number of binary
+packages by creating variants. Only binaries build for one single
+prefix <tt>/openpkg</tt> and using the default options are availabe for
+download. The OpenPKG way of deployment is to use source packages with
+build binary once, deploy to across many equal machines being a common
+scenario.
+
+<h3>Package Classes</h3>
+Packages are classified so the user can assess what quality and support
+level to expect. <b>CORE</b> packages are tweaked to work on all
+supported platforms and binary packages are provided. <b>BASE</b>
+packages build on all fully supported platforms and binaries are
+provided, too. <b>PLUS</b> packages are available as source packages
+only. They have been tested to work on all fully supported and most
+supported platforms.
+
+<h3>Source packages</h3>
+Source packages of CORE+BASE+PLUS packages are availabe for <a
+href="ftp://ftp.openpkg.org/release/<release>/SRC/">download</a>. They apply
+to all supported platforms.
+
+<h3>Binary packages</h3>
+Binary packages prebuild for <tt>/openpkg</tt> prefix
+using <tt>openpkg</tt> tag are availabe for <a
+href="ftp://ftp.openpkg.org/release/<release>/BIN/">download</a>. They
+apply only for the specific platform they were built for. CORE packages
+are available for all supported platforms. BASE packages are availbale
+for all fully supported platforms. No binaries are provided for PLUS
+packages.
+<p>
+While we strongly recommend using source packages whenever possible, the
+absence of development tools and mass rollouts are reasons which enforce
+the use of binaries. Let's make a quick'n'dirty but mostly useful check:
+
+<pre>
+$ <b>which gcc cc || echo "bad luck, no development tools"</b>
+</pre>
-This tutorial guides you on your way into the world of OpenPKG. It shows you how
-to bootstrap OpenPKG and use it to install a common and useful example application,
GNU bash. For details about
-the commands being used in this document, see the
-<a href="doc/quickref/openpkg.txt">OpenPKG Quick Reference</a>, refer to the
-<a href="doc/handbook/openpkg.html">OpenPKG Handbook</a> to dive deeper, or take
-off and have a look at the <a href="doc/slideset/openpkg.html/">OpenPKG
-Introduction Slideset</a> for a bird's eye view.
-
-<h2>Prerequisites</h2>
-OpenPKG by design makes minimal assumptions about the underlying
-operating system, but some basic things need to be checked.
-
-<h3>Platform</h3>
-The less you know about OpenPKG the more important is that you are using
-a supported primary or at least secondary [*] platform.
-The following table uses a row for each supported platform and gives
-three names for it in different columns. You will find that OpenPKG
-software uses <i>arch-os</i> to create filenames and the same ones are
-used on the ftp download site. Humans and documentation use what is
-shown below <i>platform</i>. To ensure that we really talk about the
-same thing, enter the <b>uname</b> command in a shell and find the
-output of the rightmost column.
+The matrix below tells you about all four combinations of bootstrapping or
+regular installing/upgrading a package from source or binary. For the
+tutorial, please select the bootstrap method you prefer or require. Then come
+back and <a name="matrix"></a>continue below.
+
+<h3>Security Updates</h3>
+Security updates and bugfixes are available for CORE+BASE packages. They
+are availabe for <a
+href="ftp://ftp.openpkg.org/release/<release>/UPD/">download</a> as
+source packages.
+
+<h3>Download Area</h3>
+The following table lists platforms, support level and available source
+and binary packages available from the OpenPKG download area. Please
+note that <tt>PLUS/</tt> is a subdirectory.
<p>
<box bdwidth=1 bdcolor="#a5a095" bdspace=10 bgcolor="#e5e0d5">
<table>
-<tr><td><i>arch-os</i> </td><td><u><i>platform</i></u> </td><td><b>uname
-m -r -s</b> </td></tr>
-<tr><td>ix86-freebsd4.8 </td><td>FreeBSD 4.8 </td><td>FreeBSD 4.8-STABLE
i386 </td></tr>
-<tr><td>ix86-freebsd5.1 </td><td>FreeBSD 5.1 </td><td>FreeBSD 5.1-CURRENT
i386 </td></tr>
-<tr><td>ix86-linux2.2 </td><td>Debian GNU/Linux 2.2 </td><td>Linux 2.2.22
i686 </td></tr>
-<tr><td>ix86-linux2.4 </td><td>Debian GNU/Linux 3.0 </td><td>Linux 2.4.21
i686 </td></tr>
-<tr><td>ix86-linux2.4 </td><td>RedHat Linux 9 </td><td>Linux 2.4.20-18.9
i686 </td></tr>
-<tr><td>ix86-linux2.4 </td><td>SuSE Linux 8.2 </td><td>Linux 2.4.20-4GB
i686 </td></tr>
-<tr><td>sparc64-solaris2.8 </td><td>Sun Solaris 8 </td><td>SunOS 5.8
sun4u </td></tr>
-<tr><td>sparc64-solaris2.9 </td><td>Sun Solaris 9 </td><td>SunOS 5.9
sun4u </td></tr>
-<tr><td>ix86-solaris9 </td><td>Sun Solaris 9/x86 </td><td>SunOS 5.9
i86pc </td></tr>
-<tr><td>alpha-freebsd5.1 </td><td>FreeBSD 5.1 [*] </td><td>FreeBSD
5.1-CURRENT alpha </td></tr>
-<tr><td>sparc64-solaris2.6 </td><td>Sun Solaris
2.6 [*] </td><td>SunOS 5.6 sun4u </td></tr>
+<tr><td><b>source packages</b> <td> </td><td><b>class</b></td></td></tr>
+<tr><td><a href="ftp://ftp.openpkg.org/release/<release>/SRC/">complete
release</a> <td> </td><td>CORE+BASE+PLUS</td></td></tr>
+<tr><td><a href="ftp://ftp.openpkg.org/release/<release>/UPD/">security
udpates</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><b>binary packages</b>
(<i>arch-os</i>) <td> </td><td><b>class</b></td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-freebsd4.9/">ix86-freebsd4.9</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-freebsd5.2/">ix86-freebsd5.2</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-debian3.0/">ix86-debian3.0</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-debian3.1/">ix86-debian3.1</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-fedora1/">ix86-fedora1</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-rhel3/">ix86-rhel3</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-suse9.0/">ix86-suse9.0</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-solaris9/">ix86-solaris9</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/sparc64-solaris8/">sparc64-solaris8</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/sparc64-solaris9/">sparc64-solaris9</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-solaris10/">ix86-solaris10</a> <td> </td><td>CORE+BASE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-debian2.2/">ix86-debian2.2</a> <td> </td><td>CORE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-rhl9/">ix86-rhl9</a> <td> </td><td>CORE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-suse8.2/">ix86-suse8.2</a> <td> </td><td>CORE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/ix86-gentoo1.4.3/">ix86-gentoo1.4.3</a> <td> </td><td>CORE</td></td></tr>
+<tr><td><a
href="ftp://ftp.openpkg.org/release/<release>/BIN/sparc64-solaris2.6/">sparc64-solaris2.6</a> <td> </td><td>CORE</td></td></tr>
</table>
</box>
<p>
-If your platform is not part of this list, don't panic. OpenPKG runs well on
-many other Unix platforms. There is a high probability that your particular
-platform will work, especially if it is a recent version of a major Unix
-platform such as NetBSD, OpenBSD, Gentoo Linux, HP Tru64, SCO UnixWare or QNX. For
more details of
-see <a
-href="http://www.openpkg.org/doc/handbook/openpkg.html#support-official";>OpenPKG
-handbook</a>
-
-<h3>Permission</h3>
-Additionally make sure you have root access to your system. Although it is not
-necessary to work out the whole stuff as root, we do need this in the later stages
of our example
-installation. Keep in mind that OpenPKG can be used in a limited way without having
root access but
-this is not discussed here.
+The portable nature enables additional platforms to leverage portions of
+OpenPKG technolgy on NetBSD, OpenBSD and Mandrake Linux
+[FIXME HP Tru64, SCO UnixWare and QNX]
+
+<h3>Privileges</h3>
+OpenPKG does not require root privileges to build packages. In addition,
+many packages including the bootstrap can be installed without root
+privileges but functionality might be limited. This example uses
+<tt>$</tt> to indicate a user prompt and <tt>#</tt> to indicate a root
+prompt.
<h3>Storage</h3>
-Also make sure you have approximately 250MB free disk space on the
-filesystem were OpenPKG should be loaded. The installation procedure
-creates a directory for the OpenPKG instance but it also accepts a
-pre-existing directory or a symlink to a pre-existing directory and will
-use it. The downloadable binary packages use the prefix <tt>/cw</tt> and
-so does this tutorial. However, using source packages it is possible to
-use an arbitrary prefix and in fact the OpenPKG architecture allows any
-number of parallel and simultaneous instances on a single system - until
-a critical resource is exhausted.
+Make sure you have approximately 250MB free disk space on the filesystem
+were OpenPKG should be loaded. The installation procedure creates a
+directory for the OpenPKG instance but it also accepts a pre-existing
+directory or a symlink to a pre-existing directory. The downloadable
+binary packages use the prefix <tt>/openpkg</tt> and so does this
+tutorial. However, using source packages it is possible to use an
+arbitrary prefix and in fact the OpenPKG architecture places no
+artifical limit on the number of parallel and simultaneous instances on
+a single system.
<pre>
$ <b>mkdir </b> <i>/storage/with/250MB/free</i>
-$ <b>ln -s </b> <i>/storage/with/250MB/free</i> <b>/cw</b>
+$ <b>ln -s </b> <i>/storage/with/250MB/free</i> <b>/openpkg</b>
</pre>
<h3>Workspace</h3>
Build processes sometimes take large amounts of temporary disk space.
-For our example you should have approximately 250MB of temporary
-disk space available somewhere. OpenPKG reads the environment variable
-<tt>TMPDIR</tt> to locate an hopefully large workspace.
+For our example you should have approximately 250MB of temporary disk
+space available somewhere. OpenPKG reads the environment variable
+<tt>TMPDIR</tt> to locate a large workspace.
<pre>
-$ <b>TMPDIR=</b> <i>/tmp/with/250MB/free</i>
+$ <b>TMPDIR=</b> <i>/var/tmp/with/250MB/free</i>
$ <b>export TMPDIR</b>
</pre>
<h3>System tools</h3>
We assume a Unix system with minimal toolset for binaries. Sources
-require development tools like <tt>make</tt> and <tt>[g]cc</tt> as well.
-There is no ultimate standard that tells what a minimal toolset is, so
-we have to traverse some fog here. For regular installations with an
-existing OpenPKG bootstrap, indicated by an executable
-<tt><i>prefix</i>/bin/rpm</tt>, there are nearly zero additional system
-requirements. However, the bootstrap process needs a little help and
-requires <tt>sh</tt>, <tt>tar</tt>, <tt>ftp</tt> and <tt>uudecode</tt>
-(Attention: United Linux seems to have moved this into a optional
-sharutils system package) in the <tt>PATH</tt>. Also if you want to
-install a compiler package from source, you need a vendor compiler
-first. To tell OpenPKG about your favorite <a
+require development tools like <tt>make</tt> and <tt>[g]cc</tt>
+as well. There is no ultimate standard that tells what a minimal
+toolset is, so we have to traverse some fog here. The bootstrap
+process needs a little help and require <tt>sh</tt> and <tt>tar</tt>
+in <tt>PATH</tt>. Also if you want to install a compiler package
+from source you need a compiler. Solve this chicken-egg problem
+using any exising binary compiler package from the vendor,
+OpenPKG or a third party. Tell OpenPKG about your favorite <a
href="http://www.openpkg.org/faq.html#overriding-cflags";>CFLAGS</a> and
<a href="http://www.openpkg.org/faq.html#overriding-cc";>CC</a>, see the
<a href="http://www.openpkg.org/faq.html";>FAQ</a>.
-<h2>Source or Binary</h2>
-While we strongly recommend you to use source packages whenever possible, the
-absence of development tools is the number one reason which enforces the
-use of binaries for deployment. Let's make a quick'n'dirty but mostly useful check:
-
-<pre>
-$ <b>which gcc cc || echo "bad luck, no development tools"</b>
-</pre>
-
-The matrix below tells you about all four combinations of bootstrapping or
-regular installing/upgrading a package from source or binary. For the
-tutorial, please select the bootstrap method you prefer or require. Then come
-back and <a name="matrix"></a>continue below.
-
-<h2>Release Engineering</h2>
-Those who have installed unreleased packages from CURRENT, STABLE or SNAPSHOTs
should
-be aware of the principles behind OpenPKG <a href="releng.html">release
-engineering</a>. Note that the version numbers of these packages are formatted
-as timestamps rather than what is expected from a released package. Decoding
-such version numbers yields very large integers. Any RELEASE package will
-clearly have a lower number even if it is a more mature version of the same
-package!
-<p>
-For this reason, switching from a unpublished package to a official released
-package is considered a 'downgrade' by RPM. This works by design according to the
-OpenPKG standards of <a href="releng.html">release engineering</a>. To easily
-upgrade or downgrade such uncooperative packages in general, RPM offers
-the options <tt>--oldpackage</tt> and <tt>--nodeps</tt> to be added to
+<h3>Release Engineering</h3>
+Those who have installed unreleased packages from CURRENT, STABLE
+or SNAPSHOTs should be aware of the principles behind OpenPKG <a
+href="releng.html">release engineering</a>. Note that the version
+numbers of these packages are formatted as timestamps rather than what
+is expected a release number. Decoding such version numbers yields very
+large integers. Any release package will clearly have a lower number
+even if it is a more mature version of the same package! Switching from
+a unpublished package to a released package is considered a 'downgrade'
+by RPM. This works by design according to the OpenPKG standards of
+<a href="releng.html">release engineering</a>. To easily upgrade or
+downgrade such uncooperative packages in general, RPM offers the
+options <tt>--oldpackage</tt> and <tt>--nodeps</tt> to be added to
<tt>--rebuild</tt> and <tt>-Uvh</tt> instructions.
-<h2>Matrix</h2>
+<h2>Build/Install Matrix</h2>
<img src="grid.png" usemap="#grid" border="0">
<map name="grid">
<area href="#bootstrap-source" shape="rect" coords="21,21,160,160" alt="bootstrap
from source">
@@ -145,49 +185,63 @@
</map>
<h2>Example Installation</h2>
-Select one of the four installation examples in the matrix above to begin the
-tutorial and make a regular installation of
<tt>bash-<bashver>-<release>.0.src.rpm</tt>.
+See below a video recording of a
+<a href="#bootstrap-source">Bootstrap from source</a> on
+a FreeBSD machine as a unprivileged user installing onto a NFS
+home directory. After bootstrap, the bash package is rebuild,
+installed and the bash is run.
+<img src="bootstrap.gif">
+
+<h2>More Information</h2>
+
+<h3>Fine tuning</h3>
+Do you want your shell to use the new OpenPKG environment so that you
+have the /openpkg/bin in your PATH, can read the man pages using the
+correct MANPATH etc.? There's a single command that does all of this for
+you. Place it in your favorite shell's profile.
<pre>
-$ <b>/cw/bin/bash</b>
-</pre>
-
-<h2>Fine tuning</h2>
-Do you want your shell to use the new OpenPKG environment so that you have the
-/cw/bin in your PATH, can read the man pages using the correct MANPATH etc.?
-There's a single command that does all of this for you. Place it in your
-favourite shell's profile.
-
-<pre>
-$ <b>eval `/cw/etc/rc --eval all env`</b>
+$ <b>eval `/openpkg/etc/rc --eval all env`</b>
</pre>
Enter these command examples to understand what 'eval' did for you.
<pre>
-$ <b>set | grep /cw/</b>
+$ <b>set | grep /openpkg/</b>
$ <b>which rpm</b>
$ <b>man rpm</b>
</pre>
-<h2>Want more packages?</h2>
+<h3>additional resources</h3>
+<ul>
+<li><a href="doc/quickref/openpkg.txt">OpenPKG Quick Reference</a></li>
+<li><a href="doc/handbook/openpkg.html">OpenPKG Handbook</a></li>
+<li><a href="doc/slideset/openpkg.html/">OpenPKG Introduction Slideset</a></li>
+<li><a href="http://www.openpkg.org/releng.html";>OpenPKG Release Engineering (and
package classes)</a></li>
+<li><a href="http://www.openpkg.org/security.html";>OpenPKG Security</a></li>
+<li><a href="http://cvs.openpkg.org/openpkg-re/news.txt";>New in latest
release</a></li>
+<li><a href="http://cvs.openpkg.org/openpkg-re/upgrade.txt";>Upgrading from a
previous release</a></li>
+</ul>
+
+<h3>Download Area</h3>
Browse the <a href="ftp://ftp.openpkg.org/release/<release>/">download</a> area.
<hr>
<a name="bootstrap-source">
-<h2>Bootstrap from source</h2>
+<h2>Bootstrap from source</h2>
</a>
-A warning is due for all who decide to bootstrap OpenPKG with existing OpenPKG
-installations, because bootstrapping into an existing OpenPKG hierarchy (such
-as /cw) discards the contents of its internal RPM database! When learning
-OpenPKG, it is safest to bootstrap into an empty directory which OpenPKG will
-automatically create for you if not existing.
+A warning is due for all who decide to bootstrap OpenPKG with existing
+OpenPKG installations, because bootstrapping into an existing OpenPKG
+hierarchy (such as /openpkg) discards the contents of its internal RPM
+database! When learning OpenPKG, it is safest to bootstrap into an
+empty directory which OpenPKG will automatically create for you if not
+existing.
<p>
-Should an upgrade of the actual OpenPKG itself be desired, this is not carried
-out by bootstrapping again. Rather, install the next OpenPKG version just as
-any other package. Go back to the <a href="#matrix">matrix</a> to see the
-upgrade options again.
+Should an upgrade of the actual OpenPKG itself be desired, this
+is not carried out by bootstrapping again. Rather, install the
+next OpenPKG version just as any other package. Go back to the <a
+href="#matrix">matrix</a> to see the upgrade options again.
<pre>
$ <b>cd $TMPDIR</b>
$ <b>ftp ftp.openpkg.org</b>
@@ -204,28 +258,37 @@
ftp> <b>get openpkg-<release>.0-<release>.0.src.sh</b>
ftp> <b>bye</b>
221 Goodbye.
-$ <b>sh openpkg-<release>.0-<release>.0.src.sh --prefix=/cw --user=cw --group=cw</b>
+<p>
+Choose the prefix, tag, user and group of your choice. You can omit all
+but prefix. Unprivileged users must choose their login and primary group
+which is their default anyway.
+<p>
+$ <b>sh openpkg-<release>.0-<release>.0.src.sh \\
+ --prefix=/openpkg --tag=openpkg --user=openpkg --group=openpkg</b>
$ <b>su</b>
\# <b>cd $TMPDIR</b>
-\# <b>sh openpkg-<release>.0-<release>.0.<i>arch</i>-<i>os</i>-cw.sh</b>
+\# <b>sh openpkg-<release>.0-<release>.0.<i>arch</i>-<i>os</i>-openpkg.sh</b>
\# <b>exit</b>
$
</pre>
Back to the <a href="#matrix">matrix</a>.
+<hr>
+
<a name="bootstrap-binary">
-<h2>Bootstrap from binary</h2>
+<h2>Bootstrap from binary</h2>
</a>
-A warning is due for all who decide to boostrap OpenPKG with existing OpenPKG
-installations, because bootstrapping into an existing OpenPKG hierarchy (such
-as /cw) discards the contents of its internal RPM database! When learning
-OpenPKG, it is safest to bootstrap into an empty directory which OpenPKG will
-automatically create for you if not existing.
+A warning is due for all who decide to bootstrap OpenPKG with existing
+OpenPKG installations, because bootstrapping into an existing OpenPKG
+hierarchy (such as /openpkg) discards the contents of its internal RPM
+database! When learning OpenPKG, it is safest to bootstrap into an
+empty directory which OpenPKG will automatically create for you if not
+existing.
<p>
-Should an upgrade of the actual OpenPKG itself be desired, this is not carried
-out by bootstrapping again. Rather, install the next OpenPKG version just as
-any other package. Go back to the <a href="#matrix">matrix</a> to see the
-upgrade options again.
+Should an upgrade of the actual OpenPKG itself be desired, this
+is not carried out by bootstrapping again. Rather, install the
+next OpenPKG version just as any other package. Go back to the <a
+href="#matrix">matrix</a> to see the upgrade options again.
<pre>
$ <b>cd $TMPDIR</b>
$ <b>ftp ftp.openpkg.org</b>
@@ -239,26 +302,28 @@
ftp> <b>bin</b>
200 Type set to I.
ftp> <b>cd release/<release>/BIN</b>
-ftp> <b>get
<i>arch-os</i>/openpkg-<release>.0-<release>.0.<i>arch</i>-<i>os</i>-cw.sh</b>
+ftp> <b>get
<i>arch-os</i>/openpkg-<release>.0-<release>.0.<i>arch</i>-<i>os</i>-openpkg.sh</b>
ftp> <b>bye</b>
221 Goodbye.
$ <b>su</b>
\# <b>cd $TMPDIR</b>
-\# <b>sh openpkg-<release>.0-<release>.0.<i>arch</i>-<i>os</i>-cw.sh</b></b>
+\# <b>sh openpkg-<release>.0-<release>.0.<i>arch</i>-<i>os</i>-openpkg.sh</b></b>
\# <b>exit</b>
$
</pre>
Back to the <a href="#matrix">matrix</a>.
+<hr>
+
<a name="regular-source">
-<h2>Regular installation/update from source</h2>
+<h2>Regular installation/update from source</h2>
</a>
<pre>
-$ <b>/cw/bin/rpm --rebuild \\
+$ <b>/openpkg/bin/openpkg rpm --rebuild \\
ftp://ftp.openpkg.org/release/<release>/SRC/<i>foo</i>-<i>X</i>.<i>Y</i>-<release>.0.src.rpm</b>
$ <b>su</b>
-\# <b>/cw/bin/rpm -Uvh \\
- /cw/RPM/PKG/<i>foo</i>-<i>X</i>.<i>Y</i>-<release>.0.<i>arch</i>-<i>os</i>-cw.rpm</b>
+\# <b>/openpkg/bin/openpkg rpm -Uvh \\
+ /openpkg/RPM/PKG/<i>foo</i>-<i>X</i>.<i>Y</i>-<release>.0.<i>arch</i>-<i>os</i>-openpkg.rpm</b>
</pre>
<h3>Example URL</h3>
<pre>
@@ -266,35 +331,55 @@
</pre>
<h3>Example PKG paths</h3>
<pre>
-<b> /cw/RPM/PKG/bash-<bashver>-<release>.0.ix86-freebsd4.8-cw.rpm</b>
-<b> /cw/RPM/PKG/bash-<bashver>-<release>.0.ix86-freebsd5.1-cw.rpm</b>
-<b> /cw/RPM/PKG/bash-<bashver>-<release>.0.ix86-linux2.2-cw.rpm</b>
-<b> /cw/RPM/PKG/bash-<bashver>-<release>.0.ix86-linux2.4-cw.rpm</b>
-<b> /cw/RPM/PKG/bash-<bashver>-<release>.0.sparc64-solaris2.8-cw.rpm</b>
-<b> /cw/RPM/PKG/bash-<bashver>-<release>.0.sparc64-solaris2.9-cw.rpm</b>
-<b> /cw/RPM/PKG/bash-<bashver>-<release>.0.ix86-solaris2.9-cw.rpm</b>
+ <b>/openpkg/RPM/PKG/</b> ...
+ ...
<b>bash-<bashver>-<release>.0.ix86-freebsd4.9-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-freebsd5.2-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-debian2.2-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-debian3.0-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-debian3.1-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-fedora1-openpkg.rpm</b>
+ ... <b>bash-<bashver>-<release>.0.ix86-rhel3-openpkg.rpm</b>
+ ... <b>bash-<bashver>-<release>.0.ix86-rhl9-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-suse8.2-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-suse9.0-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-gentoo1.4.3-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-solaris10-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.ix86-solaris9-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.sparc64-solaris9-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.sparc64-solaris8-openpkg.rpm</b>
+ ...
<b>bash-<bashver>-<release>.0.sparc64-solaris2.6-openpkg.rpm</b>
</pre>
Back to the <a href="#matrix">matrix</a>.
+<hr>
+
<a name="regular-binary">
-<h2>Regular installation/update from binary</h2>
+<h2>Regular installation/update from binary</h2>
</a>
<pre>
$ <b>su</b>
-\# <b>/cw/bin/rpm -Uvh \\
- ftp://ftp.openpkg.org/release/<release>/BIN/<i>platform</i>/<i>foo</i>-<i>X</i>.<i>Y</i>-<release>.0.<i>arch</i>-<i>os</i>-cw.rpm</b>
+\# <b>/openpkg/bin/openpkg rpm -Uvh \\
+ ftp://ftp.openpkg.org/release/<release>/BIN/<i>platform</i>/<i>foo</i>-<i>X</i>.<i>Y</i>-<release>.0.<i>arch</i>-<i>os</i>-openpkg.rpm</b>
</pre>
<h3>Example URLs</h3>
<pre>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/ix86-freebsd4.8/bash-<bashver>-<release>.0.ix86-freebsd4.8-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/ix86-freebsd5.1/bash-<bashver>-<release>.0.ix86-freebsd5.1-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/ix86-debian2.2/bash-<bashver>-<release>.0.ix86-linux2.2-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/ix86-debian3.0/bash-<bashver>-<release>.0.ix86-linux2.4-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/ix86-redhat9/bash-<bashver>-<release>.0.ix86-linux2.4-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/ix86-suse8.2/bash-<bashver>-<release>.0.ix86-linux2.4-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/sparc64-solaris8/bash-<bashver>-<release>.0.sparc64-solaris2.8-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/sparc64-solaris9/bash-<bashver>-<release>.0.sparc64-solaris2.9-cw.rpm</b>
-<b> ftp://ftp.openpkg.org/release/<release>/BIN/ix86-solaris9/bash-<bashver>-<release>.0.ix86-solaris2.9-cw.rpm</b>
+ <b>ftp://ftp.openpkg.org/release/<release>/BIN/</b> ...
+ ...
<b>ix86-freebsd4.9/bash-2.05b-2.0.0.ix86-freebsd4.9-openpkg.rpm</b>
+ ...
<b>ix86-freebsd5.2/bash-2.05b-2.0.0.ix86-freebsd5.2-openpkg.rpm</b>
+ ...
<b>ix86-debian2.2/bash-2.05b-2.0.0.ix86-debian2.2-openpkg.rpm</b>
+ ...
<b>ix86-debian3.0/bash-2.05b-2.0.0.ix86-debian3.0-openpkg.rpm</b>
+ ...
<b>ix86-debian3.1/bash-2.05b-2.0.0.ix86-debian3.1-openpkg.rpm</b>
+ ...
<b>ix86-fedora1/bash-2.05b-2.0.0.ix86-fedora1-openpkg.rpm</b>
+ ...
<b>ix86-rhel3/bash-2.05b-2.0.0.ix86-rhel3-openpkg.rpm</b>
+ ... <b>ix86-rhl9/bash-2.05b-2.0.0.ix86-rhl9-openpkg.rpm</b>
+ ...
<b>ix86-suse8.2/bash-2.05b-2.0.0.ix86-suse8.2-openpkg.rpm</b>
+ ...
<b>ix86-suse9.0/bash-2.05b-2.0.0.ix86-suse9.0-openpkg.rpm</b>
+ ...
<b>ix86-gentoo1.4.3/bash-2.05b-2.0.0.ix86-gentoo1.4.3-openpkg.rpm</b>
+ ...
<b>ix86-solaris10/bash-2.05b-2.0.0.ix86-solaris10-openpkg.rpm</b>
+ ...
<b>ix86-solaris9/bash-2.05b-2.0.0.ix86-solaris9-openpkg.rpm</b>
+ ...
<b>sparc64-solaris9/bash-2.05b-2.0.0.sparc64-solaris9-openpkg.rpm</b>
+ ...
<b>sparc64-solaris8/bash-2.05b-2.0.0.sparc64-solaris8-openpkg.rpm</b>
+ ...
<b>sparc64-solaris2.6/bash-2.05b-2.0.0.sparc64-solaris2.6-openpkg.rpm</b>
</pre>
Back to the <a href="#matrix">matrix</a>.
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
![[CVS] OpenPKG: openpkg-web/ bootstrap.gif releng.wml security.wml tuto...](/search?l=openpkg-dev@openpkg.org&q=subject:%22%5C%5BCVS%5C%5D+OpenPKG%5C%3A+openpkg%5C-web%5C%2F+bootstrap.gif+releng.wml+security.wml+tuto...%22&o=newest){kind=link}
