Am I right, that If I want to offer mkgmap.jar unchanged for download (well zipped) I can do this, as long as I include the LICENSE file? I want to add a script to my maps, that automatically downloads mkgmap.jar if not found, for gmapsupp.img creation. So for right now, I put mkgmap.jar plus license file onto my server (http://openmtmbmap.org/mkgmap.zip) Or am I missing something in the license? I don't want to use the mkgmap-latest download because a) mkgmap.jar is not in the base directory b) there are much more not needed files c) I don't want to put that load on the mkgmap server (don't think it's gonna be much, but could be 200-300MB daily). -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Felix Hartmann <extremecarver@gmail.com> writes:
Am I right, that If I want to offer mkgmap.jar unchanged for download (well zipped) I can do this, as long as I include the LICENSE file?
I want to add a script to my maps, that automatically downloads mkgmap.jar if not found, for gmapsupp.img creation. So for right now, I put mkgmap.jar plus license file onto my server (http://openmtmbmap.org/mkgmap.zip)
IANAL and TINLA :-) The license is GPLv2. So you may distribute binaries (which I see a jar as) if you either also distribute the source make a written offer to distribute the source The conventional wisdom is that the written offer clause is best avoided (as carrying obligations into the future). So the easy thing is to put a source .tar.gz (from which the binary jar was built) on the site as well, which very clearly satisfies your obligations, even if people choose to ignore it (see last paragraph below). For reference, here are the relevant bits of section 3: 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) - omitted, not relevant - If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
Yes I know it's GPL v2 - which doesn't mean I understand it..... Okay - so inside the download I put the information from where one can download the source, right? e.g. openmtbmap.org/mkgmap_src.zip And that src.zip should always be from the same date as the mkgmap.zip. However - what I don't understand is, why the official mkgmap-latest download doesn't include the source then...?? On 07.06.2013 16:28, Greg Troxel wrote:
Felix Hartmann <extremecarver@gmail.com> writes:
Am I right, that If I want to offer mkgmap.jar unchanged for download (well zipped) I can do this, as long as I include the LICENSE file?
I want to add a script to my maps, that automatically downloads mkgmap.jar if not found, for gmapsupp.img creation. So for right now, I put mkgmap.jar plus license file onto my server (http://openmtmbmap.org/mkgmap.zip) IANAL and TINLA :-)
The license is GPLv2. So you may distribute binaries (which I see a jar as) if you either
also distribute the source
make a written offer to distribute the source
The conventional wisdom is that the written offer clause is best avoided (as carrying obligations into the future). So the easy thing is to put a source .tar.gz (from which the binary jar was built) on the site as well, which very clearly satisfies your obligations, even if people choose to ignore it (see last paragraph below).
For reference, here are the relevant bits of section 3:
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) - omitted, not relevant -
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Felix Hartmann <extremecarver@gmail.com> writes:
Okay - so inside the download I put the information from where one can download the source, right? e.g. openmtbmap.org/mkgmap_src.zip
Sure, that would be fine. Or just have openmtbmap.org/mkgmap/mkgmap_src.zip openmtbmap.org/mkgmap/mkgmap.jar openmtbmap.org/mkgmap/index.html (or autogenerated) and consider yourself done, having made the source available in the same place. If you are only offering jars of code that is exactly a public svn revision, then I can't see anyone caring about the jar/distribution/GPL issue, but I think it is good for overall practice to be careful about it anyway.
And that src.zip should always be from the same date as the mkgmap.zip.
Yes. The requiremnt is "complete corresponding source", so that someone who knows what they are doing (with java, in this case) could rebuild it.
However - what I don't understand is, why the official mkgmap-latest download doesn't include the source then...??
My experience is that when the people who are maintaining a repo offer downloads, and it's clear to everyone that the binaries are just built From the repo, with no intent to hide anything, no one worries about the details. It's not hard to find the official sources starting with a download URL. But at http://www.mkgmap.org.uk/download/mkgmap.html I see src links, which is fully satisfactory under 3a.
On 07/06/13 15:36, Felix Hartmann wrote:
However - what I don't understand is, why the official mkgmap-latest download doesn't include the source then...??
Sorry just noticed this message. There is a mkgmap-src.zip and a mkgmap-src.tar.gz which are the source correspond to mkgmap-latest.zip. I suppose it would be more consistent to call these mkgmap-latest-src.zip etc. In all cases the *-latest* files are exactly the same as last version that was built and are just another name for it. Therefore you can always find the exact source by looking at the version number within the archive. ..Steve
participants (3)
-
Felix Hartmann -
Greg Troxel -
Steve Ratcliffe