httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Expat in tree (was: Re: [PATCH] Expat patch #3)
Date Tue, 25 May 1999 20:24:17 GMT
Bill Stoddard wrote:
> Guess I'll start paying more attention to posts in the future...
> This patch turned from adding code to the Configuration script to
> support Expat, to actually putting Expat into the code base. In your
> commit, you state "Apache elects to use the MPL license". I don't recall
> any such decision. The MPL 1.0 is not acceptable to anyone who has a
> patent portfolio. I don't think Roy can work with MPL V1.0 either. I'm
> inclined to veto this now, but I'll hold off, because I hope I'm just
> missing some of the facts.

To answer your concern, and the same that Ken expressed in a different

I believed that I had made myself clear when I first began the whole
thread: Expat would be in the code base, but could be easily *removed*
by redistributors (such as IBM) who have issues with the MPL. The MPL is
compatible with the Apache license. The reason for the "election" is to
clarify that Apache was *NOT* using the GPL (which is horribly
incompatible). In this sense, it wasn't really a "decision" per se.

There is a huge difference between providing a hook for Apache to
include Expat (pretty useless, IMO) and having it in the distribution by
default. If it isn't in the distribution, then people really can't count
on its presence; all of the work that I just did would just as well be
backed out because it would be quite useless.

I just reviewed by initial post about adding Expat (on 4/15), and I
think I was pretty clear that putting Expat in the tree was the intent
(and people can remove if it causes problems for their distribution).

Ken had a good point about whether it was under MPL 1.0 or MPL 1.1. MPL
allows us to upgrade to 1.1 if we so choose. Currently, it is under 1.0.
MPL 1.1 has not yet been published (only NPL 1.1). If we *must* back it
out until MPL 1.1 is posted, then we can. I prefer not to, and I would
definitely like to see it back in when MPL 1.1 is posted.

Also: note this addresses Ralf's question about the optional nature of
the Expat source. Configure must always be able to handle its absence
because certain distributors may need to remove it.


Greg Stein,

View raw message