Date: Wed, 18 Sep 2002 09:48:33 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Poul-Henning Kamp <phk@freebsd.org> Cc: ports@freebsd.org Subject: Re: expat2 in /src Message-ID: <7mr8fsjf6m.wl@black.imgsrc.co.jp> In-Reply-To: <77582.1032081717@critter.freebsd.dk> References: <77582.1032081717@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
At Sun, 15 Sep 2002 09:22:16 +0000 (UTC),
Poul-Henning Kamp wrote:
> 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.
Hmm. I like A). B) will make the system has two same libraries with
same functionality.
But, as seen recent commit to expat, library API may change in current
development process by current team.
Originally, expat was developped by James Clark and be stable (and not
updated) long time. Current expat 2.0 development team (releasing
1.95.5) was forked from James Clark's (with his approvement).
I cannot understand development process of current team (why they bump
library version so frequently) yet. But I worry about the library API
may be changed before 2.0 release after we import current expat
1.95.5.
So, at this time, I have no idea whther A) or B) we should go.
# One idea is importing 1.95.3 (expat.2) to base system and apply
# bugfix only. I hope expat 2.0 will have stable API and let's
# importing again 2.0.
--
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
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?7mr8fsjf6m.wl>