Date: Sun, 15 Sep 2002 11:21:57 +0200 From: Poul-Henning Kamp <phk@freebsd.org> To: ports@freebsd.org Subject: expat2 in /src Message-ID: <77582.1032081717@critter.freebsd.dk>
next in thread | raw e-mail | index | archive | help
I need to import expat2 into /src to get some basic XML reading
capability, and expat2 being both small and good fits this slot.
The (potential) trouble is, thereare some 1277 dependencies on
expat2 in the ports tree (according to INDEX).
So the simple question for the ports crew is, which option is
better:
A) Import it so it shows up in /usr/lib and /usr/include as
the official expat2, and have the ports pick up this copy
through configure.
B) Import it so it shows up as something different ("libxmlthing")
from expat2, leaving the ports to continue to use
ports/textproc/expat2 since configure will not trigger on it.
For the programs in /src which will need this, it makes no difference
which of the two we choose.
I like the fact that B) would decouple us from any version-issues
like the ones we experienced with perl. On the other hand, I wonder
if the exposure to such problems is an issue with expat2, but 1227
is a "large number of ports" in my book.
I'm not on ports@, so if somebody could please mail me the outcome
of whatever decision making process you intend to employ...
Thanks in advance!
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77582.1032081717>