Thanks Eric! What you and Jan said makes sense. It's a good thing
Robert and Don decided to use the wxWindows license ... I can see it
being a big hassle to have to distribute all of OSG at request. I
wonder why Sean didn't do so with OpenThreads?
Anyway, thanks to all for the info!
Ravi
On Feb 5, 2007, at 1:47 PM, E. Wing wrote:
Hmmm from what I understand, wxWindows basically says that I do NOT
have to distribute the source of OSG & Producer with my dynamically
linked app. But since OpenThreads uses just LGPL, I do have to
distribute its source. Is it sufficient to include a README notice
that directs the user to the OpenThreads website?
AFAIK, no. Unfortunately, if you are distributing something (L)GPL
licensesd
(i.e. the OpenThreads DLLs) you must make the source available.
Pointing the
user to the upstream vendor is *not enough*. Some Debian-derived
Linux distro
vendors learned this the hard way recently.
Jan is technically correct in that you must make the source available.
A web link is technically not sufficient. But you do have some wiggle
room. According to the license (warning: I haven't read it in a long
time so I could be mistaken and IANAL), you only need to make source
code available upon (written?) request. I believe you are also allowed
to charge a nominal fee (for shipping/handling). So if you choose, you
could not include source with your deployed binaries. But upon
request, you would be obligated to mail them a copy of the source. In
practice, this usually doesn't happen because it is much easier and
faster to follow a web link. But there are some real jerks out there
testing your full compliance with the license. Personally, if this
were to happen, I would look into the clauses about the fee and see if
I could charge a lawyer sized hourly rate to cover your time/effort.
So your options are:
1) Just ship all the binaries and hope nobody is a jerk and requests
the source directly. (If they do, you must comply, but make the fee
cover your costs and time.) A web link is sufficient for most people.
2) Ship the binaries and the source together. (If you ship on physical
medium, you might have enough space left over.)
3) Don't distribute the dependencies yourself and make the user
download them (or compile them) themselves. (This is obviously
inconvenient for end-users.)
-Eric
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
