Hello, I know very little about licensing, so I'm hoping to get some advice from you guys. In the next release of Wired, I plan to include an open-source standard cell library (or rather data derived from it). This cell library has a custom license (found at the bottom of http://www.nangate.com/openlibrary). It appears to be very permissive, but it states that the license text "must be included in all copies of the Library, in whole or in part, and all derivative works of the Library". Wired itself is BSD3-licensed. How do I arrange this in the package? Can I still have a BSD3 license for Wired? Where do I put the respective license texts? Any other things I should have in mind? Or perhaps it's better to put the cell library in its own package? I'm a bit reluctant to do this, because it means that Wired will be essentially useless on its own. Thanks, / Emil
On Mon, 1 Dec 2008, Emil Axelsson wrote:
Or perhaps it's better to put the cell library in its own package? I'm a bit reluctant to do this, because it means that Wired will be essentially useless on its own.
It's more the question, whether a Haskell wrapper to the cell library is useful on its own. I assume yes, and thus it sounds like a good idea to make separate package for a cell library wrapper.
Henning Thielemann skrev:
On Mon, 1 Dec 2008, Emil Axelsson wrote:
Or perhaps it's better to put the cell library in its own package? I'm a bit reluctant to do this, because it means that Wired will be essentially useless on its own.
It's more the question, whether a Haskell wrapper to the cell library is useful on its own. I assume yes, and thus it sounds like a good idea to make separate package for a cell library wrapper.
Well, not really. It's not a "Haskell wrapper" in the normal sense where you make a Haskell API around some code in another language. A cell library is a bunch of cell models in various formats. For example, a VHDL file gives the logical models, and another file contains tables with timing data. Wired has its own way of modeling cells (a number of classes), and what I've done is to translate the cell library data to Wired's model. So if I make it a separate package, it would have to depend on Wired. Of course, it still makes sense to have cell libraries as separate packages (I don't want to include every future cell lib in Wired). But I would like at least one cell lib to be shipped together with Wired. / Emil
participants (2)
-
Emil Axelsson -
Henning Thielemann