You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@apache.org on 2001/02/15 18:40:02 UTC

cvs commit: xml-xalan/c/xdocs/sources/xalan faq.xml

dleslie     01/02/15 09:40:01

  Modified:    c/xdocs/sources/xalan faq.xml
  Log:
  Cleaned up entry from xerces about Solaris tar problems.
  
  Revision  Changes    Path
  1.14      +4 -10     xml-xalan/c/xdocs/sources/xalan/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/faq.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- faq.xml	2001/02/15 16:45:09	1.13
  +++ faq.xml	2001/02/15 17:39:58	1.14
  @@ -103,18 +103,12 @@
   <p>For more details see: <link idref="usagepatterns" anchor="icu">Using the International Components for Unicode (ICU)</link>.<anchor name="gnutar"/></p></a>
   </faq>
   
  -   <faq title="I am getting a tar checksum error on Solaris. What's the problem?">
  +   <faq title="A tar checksum error on Solaris.">
         <q>I am getting a tar checksum error on Solaris. What's the problem?</q>
         <a>
  -         <p>The problem is caused by a limitation in the original tar spec, which
  -            prevented it from archiving files with long pathnames.  Unfortunately,
  -            various current versions of tar use different extensions for eliminating
  -            this restriction which are incompatible with each other (or they do not
  -            remove the restriction at all).  Rather than altering the pathnames for
  -            the xerces-c package, which would make them compatible with the original
  -            tar spec but make it more difficult to know what was where, it was
  -            decided to use GNU tar (gtar), which handles arbitrarily long pathnames
  -            and is freely available on every platform on which xerces-c is
  +         <p>The Solaris tar utility you are using does not properly handle files with long pathnames.
  +         You must use GNU tar (gtar), which handles arbitrarily long pathnames
  +            and is freely available on every platform on which &xslt4c; is
               supported.  If you don't already have GNU tar installed on your system,
               you can obtain it from the Free Software Foundation
               <jump href="http://www.gnu.org/software/tar/tar.html">