OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Ralf S. Engelschall
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 13-Jan-2003 15:08:41
Branch: HEAD Handle: 2003011314084000
Modified files:
openpkg-web faq.wml
Log:
clarify paragraph: gzip instead of bzip, plus more...
Summary:
Revision Changes Path
1.17 +21 -16 openpkg-web/faq.wml
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/faq.wml
============================================================================
$ cvs diff -u -r1.16 -r1.17 faq.wml
--- openpkg-web/faq.wml 13 Jan 2003 13:58:21 -0000 1.16
+++ openpkg-web/faq.wml 13 Jan 2003 14:08:40 -0000 1.17
@@ -382,23 +382,28 @@
<faq id="why-compress"
title="Why does the OpenPKG bootstrap uses %22compress%22 data format?">
- The "openpkg*src.sh" bootstrap should run on as many platforms as
- possible. All platforms within the scope of OpenPKG support
- unpacking of data that comes in "compress" format. This is true for
- very old but still in production UNIX systems. It is also true for
- very new LINUX systems which do not have an uncompress tool
- installed by default but come with a "bunzip" which can unpack
- "compress" format and is detected and used by the bootstrap. There
- is no other packed data format with equal availability.
+ The "<tt>openpkg-*.src.sh</tt>" bootstrap package should run on
+ as many platforms as possible. All platforms within the scope
+ of OpenPKG support unpacking of data that comes in traditional
+ compress(1) format. This is true for very old but still in
+ production Unix systems. It is also true for very new Linux systems
+ which do not have an uncompress tool installed by default but
+ come with at least gunzip(1) which still can unpack the format of
+ compress(1) and is automatically detected and used by the bootstrap.
+ There is no other packed data format with equal availability.
<p>
- When a user creates a "openpkg-*.arch-os-hierarchy.sh" the resulting
- script should be in "compress" format as well. This was the case in
- OpenPKG v1.0 and v1.1 and CURRENT until 20030110 and required the
- availablity of a "compress" tool to the user. As described above,
- the latest incarnations of LINUX omit that crucial tool and "bzip"
- cannot create "compress" data format. For this reason we decided to
- drop support for packing "openpkg-*.arch-os-hierarchy.sh" entirely
- beginning with CURRENT 20030113 and OpenPKG v1.2.
+ When a user creates an "<tt>openpkg-*.arch-os-id.sh</tt>" the
+ resulting script was in "compress" format as well in OpenPKG
+ v1.0 and v1.1 and CURRENT until 20030110 and. This required
+ the availablity of compress(1) to the end-user. Unfortunately,
+ as mentioned above, the latest incarnations of Linux omit
+ that crucial tool and gzip(1) cannot create the compress(1)
+ compatible data format. For this reason we droped compression
+ in the packing of "<tt>openpkg-*.arch-os-id.sh</tt>" entirely
+ beginning with CURRENT 20030113 and OpenPKG v1.2. For building the
+ "<tt>openpkg-*.src.sh</tt>" file, compress(1) is still required.
+ But this build step is a developer only step where the extra
+ installation of compress(1) is accepted.
</faq>
</ol>
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
