Derek Gaston <fried...@gmail.com> writes: > However, "binary form" isn't the only issue. You also can't distribute > things in source form under a license that further restricts its > distribution. ie - you can't distribute a libMesh based code under NDA.
I think Roy's point was that you could build an application that links (via shared library) to libMesh compiled with --disable-libHilbert. Suppose it is "fully functional" by some reasonable definition if intended function. The user could independently build another libMesh shared library using --enable-libHilbert and could use LD_LIBRARY_PATH to make the application use their other version. Any further distribution of that combination would have to comply with the GPL, but the untainted distribution would not. It would be okay for injecting the GPL'd libmesh.so via LD_LIBRARY_PATH to add functionality, but the original distribution providing libmesh.so would have to not be considered "crippled" with the expectation that the user would obtain the non-crippled libmesh.so separately as a way to dodge the GPL.
pgp1zEPlRXlMf.pgp
Description: PGP signature
------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
