From: Mark Gilbert (markgilbert@hotpop.com)
Date: Tue Mar 25 2003 - 15:48:14 EST
Thank you for the report, it has already been fixed in cvs. The problem
was due to an unbranched upgrade that wasn't tested very well.
Please note though (EAZen, feel free to highlight this) that we do not
support and in fact strongly discourage the use of peer-provided
unofficial sources by linux users, and also by almost all people who
will be building the unix frontend (mostly people on unix-ish systems).
These unofficial sources include libraries like expat, libpng, libiconv,
and popt; libraries which have pure / vanilla / not-abiword-customized /
official sources elsewhere. If the official version (not distributed by
abisource) works or is supposed to work out-of-box on your system, you
should not (in our opinion and support policy) be using the unofficial
distributions from abisource.
So why do we provide these evile creatures within the source tarball?
It is a convenience for developers on less build-friendly platforms such
as win32. All of the libs, though, should be readily available for
unix, qnx, and _some_ forms of macos[x] platform. Of course, we don't
modify so much that a library inherently useless on an arbitrary
platform would work in a form from us. So it is really just a
build-time convenience.
The one notable exception is libwv, the maintainer of which strongly
encourages the use of wv in abisource's cvs and distribution.
So, if you have or can get (as you should on linux) libxml2 or expat,
use --with-libxml2 or --with-expat when configuring abiword. Hopefully
configure will be fixed in the future to default to local libxml2 or
expat if found.
Best regards
-MG
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.
This archive was generated by hypermail 2.1.4 : Tue Mar 25 2003 - 15:56:37 EST