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: 13-Jan-2003 15:34:39
Branch: HEAD Handle: 2003011314343800
Modified files:
openpkg-web faq.wml
Log:
improve why-compress and mix in rse collision
Summary:
Revision Changes Path
1.18 +24 -22 openpkg-web/faq.wml
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/faq.wml
============================================================================
$ cvs diff -u -r1.17 -r1.18 faq.wml
--- openpkg-web/faq.wml 13 Jan 2003 14:08:40 -0000 1.17
+++ openpkg-web/faq.wml 13 Jan 2003 14:34:38 -0000 1.18
@@ -381,29 +381,31 @@
</faq>
<faq id="why-compress"
- title="Why does the OpenPKG bootstrap uses %22compress%22 data format?">
- 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.
+ title="Why does the OpenPKG bootstrap use \"compress\" data format?">
+ The "<tt>openpkg*.src.sh</tt>" source 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(1) tool installed by default but come with a gunzip(1)
+ which can unpack "compress" format and is detected and used by the
+ bootstrap. There is no other packed data format with equal
+ availability.
<p>
- 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.
+ When a user creates a
+ "<tt>openpkg-*.<i>arch</i>-<i>os</i>-<i>hierarchy</i>.sh</tt>"
+ binary bootstrap the resulting script was in "compress" format in
+ OpenPKG v1.0, v1.1 and CURRENT until 20030110. This required the
+ availablity of compress(1) to the user. As described above, the
+ latest incarnations of LINUX omit that crucial tool and gzip(1) is
+ not a full featured replacement as it cannot create "compress"
+ format. For this reason we dropped compression for binary bootstrap
+ entirely beginning with CURRENT 20030113 and OpenPKG v1.2 and now
+ keep the data verbatim.
+ <p>
+ 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]
