X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Provags-ID: V01U2FsdGVkX1/fqvcNypjfPuFgF2QRBClbHiY1uke46zA3Lb6BEq
	+4Dg==
From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
To: djgpp AT delorie DOT com
Subject: Re: ANNOUNCE: DJGPP port of Expat 2.0.0 uploaded
Date: Sat, 24 Feb 2007 21:08:03 +0100
User-Agent: KMail/1.8.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Disposition: inline
Message-Id: <200702242108.04070.juan.guerrero@gmx.de>
X-Y-GMX-Trusted: 0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l1OK8BTB015841

Am Freitag, 23. Februar 2007 19:55 schrieb Gordon DOT Schumacher AT seagate DOT com:
> 
> This is an port to DJGPP of the Expat XML library.
> 
[snip]
First, thank you for your ports.  Neitherless I would like to make some minor
comments:
  1)  It would be nice to have formated man pages instead of the raw ones.
      This formated ones must usualy be produced manualy by the porter of
      the package because the GNU Makefile does not care about this issue.
      All this implies that the porter deletes the /man/man1 (or what ever
      it is called) and repleces it with a /man/cat1 (or what ever it is
      called). In this new dir the formated man pages will be stored.
  2)  Some care should be taken when the manifest files are produced.
      Manifest files should usualy not contain directory paths or the complete
      containt of the directory may be deleted.  As an example I will show this
      using expat20b.mft:
bin
bin/xmlwf.exe
[snip]

      If the user starts the command rm -vfr @manifest\expat20b.mft, not only
      the intended binary bin/xmlwf.exe will be deleted, but also the complete
      /bin directory with all its containts.  This is certainly not intended
      neither by the porter of the package nor by the user.
  3)  It should be taken care that the file names conform to the 8.3 file name
      restriction.  Example given:
docs
docs/expat-2.0.0
docs/expat-2.0.0/expat.png
[snip]

      On an SFN system the name /expat-2.0.0 will not be unique.  One unzip
      program may translate this as /expat-2.0-0 another one may convert this
      to /expat-2.00 or something else.  This will have nasty consequences if
      it is the name of a header or a library.  It is responsability of the
      porter to choose appropriate file names that conform the 8.3 file name
      restriction.


Finally again, thank you for the port.

Regards,
Juan M. Guerrero