Looking for a Licenseing
lazarus / 8-Other

----------------------------------------------------------------------
captian jaster · 2010-09-25 01:33

I want to find the right licensing and I have some question's..
I am using the zlibar source but I don't wanna release my source...
Can I make it so I just set the right credits to point to the correct
people
Whats the best license for this?
Thanks

----------------------------------------------------------------------
bflm · 2010-09-25 08:46

Quote from: captain jaster on September 25, 2010, 03:33:09 amI want to
find the right licensing and I have some question's..
I am using the zlibar source but I don't wanna release my source...
Can I make it so I just set the right credits to point to the correct
people
Whats the best license for this?
Thanks 

If you mean this zlibar:

http://wiki.freepascal.org/Zlibar

then it's license is very clearly stated there. You can't relicense
other's work w/o the author(s) permission, but you are (simplistically
said) allowed (as it's LGPL) to use the library in a closed source app
while you include the original work LGPL license plain text with your
binary distribution and you haven't modified the original work, just
linked to it from your app. The optional credits in some about box are
an optional nice thing to do, but that's not enough to fulfill the
LGPL requirements.

----------------------------------------------------------------------
captian jaster · 2010-09-25 15:51

So I just have to link the lgpl?
Do I have to compile it into the binary or can I link/load it from a
txt file?

----------------------------------------------------------------------
bflm · 2010-09-25 16:15

Quote from: captain jaster on September 25, 2010, 05:51:44 pmSo I just
have to link the lgpl?
Do I have to compile it into the binary or can I link/load it from a
txt file?

I can't ATM check the exact license version - the Lazarus Wiki is down
right now. When it come back check the texts here (if it's pure LGPL,
otherwise check the original license):

http://opensource.org/licenses/lgpl-license.php

Usually you don't have to compile in the license text. Usually also
it's not enough to link to it. Usually you are obligated to distribute
the original license text as part of the documentation of your
application, i.e. reprinted in the docs or as a separate, human
readable file included with your binaries, e.g. LICENSE-ZLIBAR. Then
you "link" from your docs/about box to the fact, that your app is
using a LGPL licensed 3rd party library and where the license text can
be found in the installation tree. At least this is roughly how it
works in licenses I'm used to, but IANAL, so please double check this
for your own good, because maybe it also is enough to put all of the
above to the app about box (the credits and the full foreign license
text).

----------------------------------------------------------------------
captian jaster · 2010-09-25 16:22

Ok Thanks for the info