Svein Ove Aas <svein....@aas.no> writes: >>> when writing a Haskell library that uses two other Haskell libraries -- >>> one licensed under BSD3 and one under LGPL -- what are allowed >>> possibilities for licensing the written package?
>> Any resulting binaries might contain a mixture of such libraries, and >> the most restrictive license will usually be the license of the result. > In this case, LGPL is a problem. It requires you to offer a way to > re-link such binaries against new versions/implementations of the > library, which in practice requires it to be either open source or > dynamically linked. Isn't it possible to provide the proprietary bits as compiled object files (.o or .a) to be linked by the recipient? -k -- If I haven't seen further, it is by standing in the footprints of giants _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
