On Wed, Dec 06, 2000 at 12:47:37AM +0100, Kaiserovi wrote:
> Wait. Sablot 0.44 *is* using jclark's expat 1.1. The sources are just
> the same; only the makefiles for use with Sablotron are added.
That's not really the issue though - it's a bad idea to distribute
a different set of tarballs from his sets. Sablotron shouldn't provide
any custom Makefiles for expat, it should just use it's own Makefiles
and test for an installed set of libs.
If you want to offer a _mirror_ of his tarballs, that's fine, but
if you do anything else, you force someone to choose which
Expat they are going to install - which causes a problem as soon as
someone wants to use Expat for something besides Sablotron.
The two tarballs I looked at - from jclark's web site, and from
Sablotron's, were completely different - at least in structure,
which is bad enough.
Also, the Sablotron web page, even after the redirect once you click
on the download link, seems to send some extraneous data chunks after
the file is sent. What OS/server combo is that?
> Expat 1.1 was the last production release before the new expat 1.95 (Oct
> 21, 2000). Expansion of parameter entities was only supported in a test
> version of expat. In spite of the advantages of the latter, we decided
> to use the stable version.
>
> Now that expat 1.95 exists, there's no question about what to use, and
> the next release of Sablot (0.50) will switch to it.
As a seperate item - jclarke needs to put the version number in the
filename of his expat.zip, and maintain a couple versions back, to
simplify maintainence for people who write package install tools.
--
David Maxwell, [EMAIL PROTECTED]|[EMAIL PROTECTED] -->
If you don't spend energy getting what you want,
You'll have to spend it dealing with what you get.
- Unknown
