This is because many applications are
written for in-house consumption, simple web sites, etc. and those
applications are not GPL.
In-house use cannot violate the GPL. The GPL requires that source be made
available without further restrictions, but only to those to whom the app is
distributed.
I created closed source Postgres/mySQL client application.
When using PostgreSQL as backend I can include Postgres server binary code
in my application distro.
When using mySQL my application setup can load mySQL server installation
package from mysql website and execute it automatically.
Andrus [EMAIL PROTECTED] writes:
I created closed source Postgres/mySQL client application.
When using PostgreSQL as backend I can include Postgres server binary code
in my application distro.
When using mySQL my application setup can load mySQL server installation
package from mysql
In the last exciting episode, Andrus [EMAIL PROTECTED] wrote:
I created closed source Postgres/mySQL client application.
When using PostgreSQL as backend I can include Postgres server
binary code in my application distro.
When using mySQL my application setup can load mySQL server
That doesn't sound consistent with the arrangements that MySQL AB
expect for commercial users of their products.
They indicate assortedly that:
- If you are developing and distributing open source applications
under the GPL, or some OSI-approved license, you are free to use
MySQL(tm) for
applications are not GPL. It's mostly commercial apps that end up
getting the license because businesses fear lawsuits more than
individuals do (something like music piracy in which end users copying
a CD to their disk drives are much less likely to be sued than if you
produce products that
