On Jan 7, 2014, at 7:24 AM, Yongming Zhao <ming....@gmail.com> wrote:
> according to > http://www.apache.org/legal/3party.html#options-systemrequirements : >> System Requirements >> >> If a PMC wishes to build a product that takes a core dependency on some >> third-party work that is only available under an excluded license, the PMC >> might consider whether the work can be used as a system requirement, rather >> than an internal part of the product. The drawback to this approach is that >> every new system requirement narrows the potential user base for the >> product. Each PMC is solely responsible for choosing an appropriate set of >> system requirements for its products; however, the following guidelines are >> recommended: >> >> • Clearly label each product's system requirements and their licenses >> on the main product page. >> • Consider the project's implicit/explicit charter and intention of the >> board resolution that created the project when determining how the system >> requirements will affect the users. >> • Provide a means, when practical, for users to substitute an >> alternative implementation for system requirements only available under >> excluded licenses (especially non-OSD licenses). > > > I’d prefer to not link GPLed library if we have another alternate > replacement, we have seen many works on OpenOffice.org for GPLed library > replacement. > > I think it is safe to replace readline because the other two replacement is > very often used too, that will make much dependency issue for our users. That makes sense to me. I'm OK with the change, I mainly wanted to raise it on the mailing list to give the larger community an opportunity to chime in. J
