Thank you for your reply, Dirk. > The core libraries are all LGPL, if there are some headers that have other > licenses listed that's an oversight and can be fixed. > > Contrib is a different story. Most Contrib libs are separate libs because > they > depend on other libs that are either non-standard in the sense that they're > not > part of most distributions, or because they're not LGPL, and thus the Contrib > lib can't be LGPL. There are some pieces that have been contributed under > non-LGPL terms, and are therefore not part of the core. I see.
> Which Contrib libs are specifically important for you? VideoGrab and Physics. Currently, we are using VideoGrab libraries. In future, we might use Physics libraries. > Sideline: Unless you have a very good reason I would start using the current > GIT > head of OpenSG 2.0, as that is significantly easier to use and better > designed > in some core areas. Thank you for your recommendation. We will examine positively to migrate for 2.0. Thank you. On Sun, 02 Oct 2011 22:56:15 -0500 Dirk Reiners <dirk.rein...@gmail.com> wrote: > > Dear Kazuhiko Kido, > > On 10/02/2011 08:50 PM, 木戸 和彦 wrote: > > Hi all. > > > > I'd like to make sure that all OpenSG libraries (include contrib libs) > > are LGPL license, aren't they? License description in source code header > > seems to say GPL license. (e.g. OSGAttachmentContainer.h, OSGAVCodec.h > > and so on) > > The core libraries are all LGPL, if there are some headers that have other > licenses listed that's an oversight and can be fixed. > > Contrib is a different story. Most Contrib libs are separate libs because > they > depend on other libs that are either non-standard in the sense that they're > not > part of most distributions, or because they're not LGPL, and thus the Contrib > lib can't be LGPL. There are some pieces that have been contributed under > non-LGPL terms, and are therefore not part of the core. > > Which Contrib libs are specifically important for you? > > Sideline: Unless you have a very good reason I would start using the current > GIT > head of OpenSG 2.0, as that is significantly easier to use and better > designed > in some core areas. > > Yours > > Dirk > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Opensg-users mailing list > Opensg-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/opensg-users -- Kazuhiko Kido <kido.kazuhiko...@canon-its.co.jp> ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
