* walton@12on14.com [07-23-10 08:24]:

Can someone help? Is there an easier way to comply? Or, am I reading the wrong license terms?

I believe redirects will satisfy the license.

On Fri, Jul 23, 2010 at 4:21 PM walton wrote:

sure).  It appears that I must make available the source code. I have no problem with that, but there is no single zipped file of the many hundreds of files for GIMP. Each file must be downloaded then put into a directory . . . recreating the entire directory tree.

You have me at lost :)

What files? Are you talking about source code of GIMP? If so, what is exactly the problem of uploading an archive of GIMP's source code or even linking to it?

And by the way, why do you need to distribute source code? Did you apply changes to it?

Alexandre Prokoudine http://libregraphicsworld.org

On Fri, 23 Jul 2010 16:31:33 +0400, Alexandre Prokoudine wrote:

And by the way, why do you need to distribute source code? Did you apply changes to it?

The GPL requires that the source code is available together with the binary (or that you give a written notice to provide the source code on request). This is further clarified in the FAQ: http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#SourceAndBinaryOnDifferentSites

On Fri, Jul 23, 2010 at 2:31 PM, Alexandre Prokoudine wrote:

And by the way, why do you need to distribute source code? Did you apply changes to it?

You need to. In fact, the sources are supposed to be available to the end user for 3 years after the user obtains the binary. And you must ensure they are available, which is taken to mean "You must put it somewhere where you can reasonably control the availability" or something along those lines.

On Fri, Jul 23, 2010 at 5:44 PM, Branko Vukelic wrote:

You need to. In fact, the sources are supposed to be available to the end user for 3 years after the user obtains the binary. And you must ensure they are available, which is taken to mean "You must put it somewhere where you can reasonably control the availability" or something along those lines.

Okay :) So what is the problem of uploading an archive? :)

Alexandre Prokoudine http://libregraphicsworld.org

On Friday, July 23, 2010 10:18:21 am walton@12on14.com did opine:

I am writing a user book on GIMP, and in conjunction with making available several excerpts (tutorials), I put GIMP 2.6.8 for windows on my site, along with the users manual, and related Python files.I would like to comply with the GPL (I spent several hours just trying to figure out which license requirements apply to GIMP, and I am still not sure).  It appears that I must make available the source code. I have no problem with that, but there is no single zipped file of the many hundreds of files for GIMP. Each file must be downloaded then put into a directory . . . recreating the entire directory tree.  That would take many days, days of not writing, and I would make mistakes--omissions or duplications--with no practical way of knowing correcting them.Can someone help? Is there an easier way to comply? Or, am I reading the wrong license terms? Walton

Pleased do not post with html enabled. For those of us, who for security reasons, do not enable html rendering in our email agents, all the html coding does is expand the message, sometimes to hundreds of times its size in straight text and makes it very hard to locate your actual message in all that folderol.

This is std netiquette.

On Fri, Jul 23, 2010 at 3:51 PM, Alexandre Prokoudine wrote:

Okay :) So what is the problem of uploading an archive? :)

Usually it's either forgetfulness or lack of knowledge as to GPL requirements. Also, nobody says you have to distribute source on the server (but it's easy). You can also give your users a written promise that you will send them the CD with the source _on request_ and if you _pay_ for the CD and related costs.

On Friday 23 July 2010, walton@12on14.com wrote:

I am writing a user book on GIMP, and in conjunction with making available several excerpts (tutorials), I put GIMP 2.6.8 for windows on my site, along with the users manual, and related Python files.

I would like to comply with the GPL

--------snip----------

Can someone help? Is there an easier way to comply? Or, am I reading the wrong license terms?

OK I've read your mail and the other responses so far.

If I understand it you are writing a book and you want to distribute the GIMP program with it (probably on CD).

I am not a lawyer but what is wrong with just supplying the source archives (.tar.gz, .bz, etc) on the same CD. As far as I can see this would alleviate your need to maintain a web server to provide the source code. You would need to include the source archive for each version of GIMP included on the CD (Windows, BSD, Mac, Linux, QNX, etc) as well as source for any other GPL programs you include. These archives are available wherever it is that YOU get the programs from. (Assuming the sites are in compliance w/ the GPL). The GPL also requires the use of the "COPYING" file, you may want to include this in the root directory of the CD/DVD

My understanding is that, while the GPL does stipulate making the source code available, there is some leeway in how you make it available. I believe you could even publish the actual code in your book if you desired,and be in compliance with the license. (Of course this would probably require more pages than your whole book)

If you are distributing tutorial files and examples then you need to comply with the associated licenses for those files as well (CC, Artistic, BSD, etc)

If I am wrong about any of this then I am sure a more knowledgeable source than I will jump in and correct me.

see ya dh

On Fri, 23 Jul 2010 11:27:00 -0700, David Herman wrote:

You would need to include the
source archive for each version of GIMP included on the CD (Windows, BSD, Mac, Linux, QNX, etc)

Since GIMP for these systems compiles from the same source, it's enough to include a single copy of it on the CD.

On Friday, July 23, 2010 03:49:57 pm walton@12on14.com did opine:

Please accept my apologies. I am new to this forum.

walton

NP Walton, I really wasn't trying to be a list enforcer, just reminding.

1. Welcome to the list, enjoy. There are some pretty smart folks here. It doesn't seem to be a high traffic list.

2. Now, please ask your question again so that those who can answer it authoritatively, might do so.

3. Please try to keep your replies to the list so that others might be able to search the list archives and possibly find the answer.