BSD, PHP, Apache and GPL licenses

Well, the BSD and MIT licenses are very straight forward, provide a copyright and you're good to go.

The GPL though, seems a little less straight forward, with much more lawyer speak that the other two. It seems to be a longer version of the other two with a few added clauses.

If you redistribute it in binary form, you have to offer the source code. If you change the source code you have to say so and give the date.

Essentially it's keeping GPL software open source whereas you can provide a BSD or MIT program in binary form without offering the source.

The reason I ask is because I'm using a few programs which are open source under these licenses and I was trying to figure out if I could distribute them with the PHP software I wrote which uses these programs. It's written for windows and I have a batch file which will install and start the software and services.

It distributes, unmodified:
Apache 2.2 (Apache GPL style license)
PHP 5.2 (PHP Apache Style License)
CRONw (GLP)
WGet (GPL)
PostgreSQL (BSD)
Perl/vanilla Perl (GPL)
Turk MMCache (GPL)
My PHP Source, encoded with Turk MMCache (My LIcense)

The OSI describes the BSD license as the MIT license, but there is a slight different in the wording.

I'm _pretty sure_ I can distribute an archive package with the installers for all of these so long as I meet the 'easy to abide' terms of the licenses without being charged a fee.

Any comments would be greatly appreciated.

You should be fine as long as you are not linking directly to GPL'd code, and you supply references in the documentation for how the source code for the GPL'd components can be obtained. You mostly need to be careful with GPL'd libraries, since they apply the license virally. Most of the times the developers should have used the LGPL, but niavely didn't.

As long as you show good faith and attempt to work with the license as per your understanding of what is acceptable, you should not have any problems.