> > I'd have sweared MySQL, but they require your app to be opensource,
>
> What? MySQL is licensed under the GPL, this in no way requires your application
> to be open source.

You speak wisely. I've just read something I had missed:

Free use for those who never copy, modify or distribute. As long as you never distribute (internally or externally) the MySQL Software in any way, you are free to use it for powering your application, irrespective of whether your application is under GPL license or not.

> But if MySQL is only part
> of your program, you can close all of your code and simply interface with MySQL
> and require that MySQL be installed, which is still untouched by your code.

Right, that's the case, I only need the database to work.

> I have made quite a few applications for businesses that required Apache, Perl,
> Mozilla, and other things. My application did not have to be open source
> (though it is), because my application was completely seperate from those, even
> though it required them to be installed to work.

I think what will be what happens here.

> Anyway what are you programming? Maybe I can give you some ideas of how to work
> with the software licenses.

Actually I am not programming, but your help would be valuable nonetheless.

A person asked some guy to program something for his business, and asked me to see this guy to check the technical side of his work. He'd have had me do the job, but I'm too busy with my thesis. I offered some supervision, though.

The software is about a database accessed from clients on a lan with GDI applications, and maybe via web with applets. We agreed to have everything done in a platform-independent, free-based environment, so that the guy buying the software can switch OS without rewriting everything and spending as little bucks as possible. The programmer is one of those coding machines that just need to be told what to do, so I stepped in. We ended up with MySQL for the database, Java2SE for the program, Apache for the webserver that will host the applet. This way the business guy should have no commercial licence to care about.

Another important point was: the business guy works for a chain that, if the software was good, would buy it and resell it to all the businesses in the chain, and maybe even others. In this perspective, we need the software to be distributable, and paying for other licenses would make it less cheap and thus less interesting. I made my choices with this in mind as well, I guess I'll need to read the license agreements more carefully before the final "go".

The software will surely need to be updated in the future, too, and we wish to be indipendent from the guy writing it now, not because he's bad, but because anyone using it could have to customize some part. So the programmer was asked to sell every right to the source code too, which he agreed. I suggested him to use Eclipse, or another well known IDE, to organize the project, and to document the software with Doxygen, which makes it easier to understand what code does, and he said that was ok.

I'd go into details, but it's damn late now. Maybe later.