Re: [Nano-devel] 2.5.1 little fry

[Chris Allegretta]

I think the best part of this troll is that the email is flagged as
Spam on my system.  Just because I don't come to your house and show
you how I build the binary does not mean "OMG GPL VIOLATION LULZ"

For those interested in a genuine discussion of nano and the the terms
of the Cygwin source, please see the old thread at
http://lists.gnu.org/archive/html/nano-devel/2003-04/msg00003.html

Per that thread, I have admittedly forgotten to re-copy the Cygwin
source to new NT/ subdirectories on the FTP site (though that's NOT
part of any requirement of the license), but the original Cygwin
source I'd used is still in place at
ftp://ftp.nano-editor.org/pub/nano/v1.2/NT/cygwin-1.3.19-1-src.tar.bz2.
Regardless, I've created a new directory at a higher level in the FTP
tree, ftp://ftp.nano-editor.org/pub/nano/win32-support/ and placed
both the source what should be the version of Cygwin nano.exe is built
from nowadays, as well as the source for PDcurses, into that
directory.  PDCurses is in the public domain and thus has no binary
redistribution requirements, so it is included there as a convenience
only.

Again: IT IS NOT a GPL violation to use additional libraries in nano
win32 binaries that I distribute, given that I:
- Made no modifications to the nano source code to produce that binary.
- Made no modifications to the cygwin source code to produce that binary.
- Made no modifications to the PDCurses source code to produce that binary.

The requirements of the win32 build are ENTIRELY provided by PDCurses
and Cygwin. Therefore, the ONLY requirement in question here is that I
also make available the source code to those tools, which I did years
ago, and continue to do.


On Wed, Jan 20, 2016 at 7:42 AM, frank <address@hidden> wrote:
> On 19/01/2016 16:30, Benno Schulenberg wrote:
>>
>> Okay.  But what happens if -- $FATE forbid -- you get run over
>> by a bus tomorrow?
>
>
>
> A relevant question. And still in my mind the GPL violation ranks more
> urgent and relevant.
>
> The nano code includes the headers types.h and pwd.h for types like uid_t
> and gid_t and functions like getpwuid. These types and functions apply to
> unix-y file systems, they do not apply to NTFS. So the tricks to build the
> official nano.exe have to disable or replace the entire content of the two
> headers - which is not reflected in the source released.
>
> Looks like a license infringement by the maintainer of a GNU project.
>
> Regards
>
>
> frank
>
>
>
>
> _______________________________________________
> Nano-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/nano-devel