You cant mix open source gpl'd code with close source, its against the gpl.
I was under this impression as well.
huisinro, you say" search "Huihong Luo" on VirtualBox source code changelogs, you will see some of our code changes."
I should not have to go back to the Virtual Box website, your base program, to find these changes. They should be prominently posted on Your website. What if I never heard of Virtual Box but only your program?
huisinro - Your missing the point. According to my understanding of the GPL once you add closed source to an open source GPL licensed application, you cannot redistribute it without providing access to all of the source code, Virtual Box's AND your closed source changes. Your closed source is Not closed any longer. By virtue of adding it to an App under GPL, your closed source becomes open source and you must provide the source code for it.
Your own license text even says this !
I Quote from YOUR License text that you distribute with VMLite:
In your own license you give with the VMLite, you only give the version for Virtual Box. But it does state:
"For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that
we gave you. You must make sure that they, too, receive or can
get the source code. If you link other code with the library, (This would be Your VMLite Closed Source Code)
you must provide complete object files to the recipients, so that
they can relink them with the library after making changes to the
library and recompiling it. And you must show them these terms so
they know their rights. "
It reads to me that this also applies to your modified closed code.
I want all source code and all of your object files that you linked with the libraries so I can "relink them with the library after making changes to the
library and recompiling it."
According to the GPL and the license you provide me, this is MY right as I understand it. Where can I download YOUR Object files? You have Not provided or offered these things.
I will quote the GNU GPL FAQ:
" Does the GPL require that source code of modified versions be posted to the public?
The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization.
But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL.
Thus, the GPL gives permission to release the modified program in certain ways, and not in other ways; but the decision of whether to release it is up to you. "
AND,
" If I use a piece of software that has been obtained under the GNU GPL, am I allowed to modify the original code into a new program, then distribute and sell that new program commercially?
You are allowed to sell copies of the modified program commercially, but only under the terms of the GNU GPL. Thus, for instance, you must make the source code available to the users of the program as described in the GPL, and they must be allowed to redistribute and modify it as described in the GPL.
These requirements are the condition for including the GPL-covered code you received in a program of your own. "
The GPL Violations page says:
"If you think you see a violation of the GNU
GPL,
LGPL,
AGPL, or
FDL, the first thing you should do is double-check the facts:
- Is source code included in the distribution?
- Is a written offer for source code included with a distribution or just binaries?
- Is the available source code complete, or is it designed for linking in other non-free modules? "
So you see, you have not fully answered my question. How can you side step the GPL and not provide the full source code? You do not even have a link on your site to the source code for the Virtual Box OSE version itself, let alone your closed source changes.
Like I said, I do a lot of advertising for VMLite, and people want to know this. I need something that is solid to tell them. So far you have not answered this.
You have admitted you changed the original as well as added closed source to the code.
I quote huisinro, "We have contributed our changes to the VirtualBox OSE,"
Where is your source code for this? You have not even provided this. Aside from your closed source, Not providing the source code for changes made to the original code is Clearly a major violation of GPL. There is no place on your download page to download any source code at all.
You do have another license in your software.. one for your closed source. You cannot do this. The two license agreements conflict with and contradict each other. Because you based your end product on the VBox OSE, you cannot have another license to cover your closed source. This makes your closed source code license Null and Void. Because your closed source license, is not legal, I ask that you provide me full source code (both the changes you made to Virtual Box OSE and your closed source code) and all object files. I want to make my own application based on your software. According to the license for your base program, Virtual Box OSE, and it's GPL License, this is My Legal Right as I understand it.
You seem to fail to understand, that when you decided to modify and add code to the Virtual Box OSE, to create VMLite, you ACCEPTED it's GPL License in it's entirety. Anything you do to the software including making a new application from it, must remain fully under that same GPL License - This includes your closed source additions.