Hello Leon,

IMO the libraries have very little value without the source code being available under an OS license. In my experience this view now also applies in the corporate environment; managers want to stay away from free binary packages since they cannot know how the code actually works and what exactly it does. Another thing is that if you are using a free binary package and stumble on a bug, there is no way to fix it.

Anyway, you cannot apply an open source lisense in a binary package with no source ;-)

just my 0.25.

Manos



Leon Rosenberg wrote:

I'm sorry for OT, but I am pretty stupid with legal stuff, and after
carefully reading gnu und apache license packages I am as unknowing as
I was before. Here my problem:

I am trying to convince one of my customers to make some of the libs I
wrote for him public available. For process reasons the source code of
the libs will not be available, only the jars would be available and
redistributeable. I thought publishing the jar under the LGPL would
make it, but after reading http://www.gnu.org/licenses/lgpl.html I'm
starting to doubt it.

Since we must have many experts in licensing here, I think there is no
better place to ask :-)

The jars would be free for copy, modification, usage, all the gpl
stuff, but not available in sourcecode. This is because the company,
which owns the code, has to make additional reporting to the
headquarters in case they would publish the source code and ensure,
that there are no comments in the source code, that contain
non-disclosure information. Publishing the jars only would be lot of
easier for them, and the probability, that they would do it, is
higher. So under which license do they need to publish the jars?

Or is it something which can be achieved by a trick? Creating a dummy
application which contains the jars and put the application under
lgpl, therefore providing source code for the application, but no
source code for the libs?

any help is highly appreciated

regards
leon

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to