search

Pelagicore / meta-bistro

Yocto layer providing In-Vehicle Infotainment related functionality and adaptations
MIT License
14 stars 21 forks source link

Are we still using libitzam? #22

Closed jeremiah closed 8 years ago

jeremiah commented 8 years ago

In recipes-support there is a recipe for libitzam. This code is dual licensed -- simplified BSD for open source projects like ours and commercial license for closed source projects. If we want anyone to use meta-bistro, we need to make it clear that using libitzam commercially requires a commercial license from upstream. More here: http://coyotegulch.scottrobertladd.net/products/itzam/c/index.html

If we're not using itzam, perhaps we remove this in order to avoid any confusion for downstream?

tobsan commented 8 years ago

If I'm not mistaken, itzam is the default backend for persistence common object from GENIVI. However, according to the docs, it is no longer supported, and users are encouraged to use key/value store instead.

The recipe in recipes-extended/persistence-client-library/ DEPENDS on libitzam. However, a recipe for PCL, PCO and libitzam exists in meta-ivi nowadays (and maybe has for a while). Imho, it does not make sense to need libitzam without wanting PCO, and then you'd want meta-ivi anyway.

Perhaps @rpannek can remember if we had some super unique use case back in the days, but I don't think we did.

rpannek commented 8 years ago

You're right, I think we added it there just before it was depricated in PCL but never really used it. And it was depricated because of the license problems if I'm not mistaken. So as far as I can see we can just remove it.