On Feb 9, 2013, at 9:51 AM, Brice Goglin <brice.gog...@inria.fr> wrote:
> You know their usual license, but you can't check at runtime that the > libnuma/libxml/libpci you're actually linking to is the usual one with > the license you expect and not another one with same ABI but different > license. Sure, I understand that, but my point is that the set of libraries hwloc will use is fairly small -- the space is finite and examinable (by developers at development time). When we choose to link in a new library to hwloc, it's possible to do the due diligence and know if there's a possibility if we'll be including GPL taint. For example, if someone writes a GPL version of libnuma someday, we'll be lying in our configure. But the chances of that happening are incredibly small. Right now, we know that if we link in libpci, there's a possibility that we're introducing GPL taint -- and we should therefore avoid it unless specifically requested. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
