Quake III tools GPL

http://www.qeradiant.com/

I wonder what impact this has on selling content created
with these tools. As I understand, you can't use the output
of these tools in a commercial product.

Thanks for posting this. Somehow I missed it.

i'm not 200% sure, but you actually can release commercial titles under the GPL license they provide... you've just gotta be careful about a certain number of details...

--Mike

Mmm, looks complex - I'm not sure what a 'tarball' is.

TAR is short for Tape Archive, and is essentially a fileformat that rolls a bunch of smaller files into one large one. This resulting file is often referred to as a 'tarball'. It's predominantly a UNIX/Linux standard, although WinZip can extract files from TAR as well.

(The tar file can optionally be compressed as well, using a compressor like gzip. Most of the time those have a .tar.gz file extension.)

If two pieces of software are mutually exclusive, the software that is GPL'ed does not affect the other software's license. Data created in GPL'ed software is not affected by the GPL. If you modify the program, of course, you'll have to release the full source code to it.

But, as it stands, these are two stand-alone tools that (given modifications) could be modified to be used for anything.

Not sure either - for the Quake III engine GPL meant releasing your source (I *think*), but what code is anyone likely to marry with that of the tools? I dislike GPL... nobody ever seems 100% sure what it means.

[DOUBLE POST COURTESY OF FIREFOX]

There was some Talk of this on the Torque Forums as well as on here before , No one seems 100% sure.
While it seems you could use Q3radiant for bsp production ..it would would only be the Exact version included with in the source.

But Like I said, no one seems to be sure about this.

Sam

You modify the code, you release the code and all code that links to it in any way (as long as it's actually linking during compile time, or if it's part of the same project). If two projects are mutually exclusive and you are using one project to produce data (BSPs) for another project, the two projects are technically mutually exclusive and thus the GPL'd project does not affect the license of the non-GPL'd project.

Same applies to data read by a GPL'd application. Just because it can read and write data doesn't mean the data is part of the project. The project is the specific work that creates the data, not the data produced by said project.

1am, my eyes hurt, I have painkillers in my system -- needless to say, if none of that made sense, you're probably not alone.