public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Martin Guy <martinwguy@gmail.com>
To: Mau Z <zmau1962@gmail.com>
Cc: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>,
		"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Q: whald should I give my "customers" ?
Date: Tue, 31 Dec 2013 18:57:00 -0000	[thread overview]
Message-ID: <CAL4-wQrNQH-8tw1tMBYymVP7MEq7Jom+wUbssUJkG5SSrnfm2g@mail.gmail.com> (raw)
In-Reply-To: <CAPFcPTK8Jppp=k=L9O0k_DcFtDvey-MR_ujvcv8bQuzRn1Drsg@mail.gmail.com>

On 31/12/2013, Mau Z <zmau1962@gmail.com> wrote:
> I have no  problems with licenses (all in the same city).

You may not, but the GNU foundation and your customers may!

If you give executables of GPL-ed software to people, you must also
make available to them the sources used to created those binaries: the
tarballs of the binutils, gcc, glibc sources and, of course, of the
build system used to compile them (crosstool-ng).

That is the *letter* of the law. The *spirit* of the law is to put the
users of the software in a position to rebuild the software they are
using from source, exactly the same way that you did, so that they can
fix bugs, make modifications, reconfigure and so on.

In practice I have knowingly broken the letter of the GPL in the past,
by distributing patch sets to GCC or crosstool and the resulting
cross-compiler binaries, since the patches and build system were a few
K, the full sources were hundreds of megabytes and my inet connection
was from home at a few 10s of K per second.
  In theory you should offer to provide the sources yourself. In
practice, supplying build instructions for publicly-available packages
such as unmodified crosstool-ng and the things it downloads seems to
be acceptable.  It certainly achieves the goal of the GPL, which is to
give the users freedom.

Cheers

    M

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2013-12-31 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 22:41 Mau Z
2013-12-30 22:58 ` Yann E. MORIN
2013-12-30 23:07   ` Mau Z
2013-12-30 23:09   ` ANDY KENNEDY
2013-12-30 23:18     ` Mau Z
2013-12-31 18:57       ` Martin Guy [this message]
2013-12-31 19:40         ` Baruch Siach
2013-12-31 21:29           ` Mau Z

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL4-wQrNQH-8tw1tMBYymVP7MEq7Jom+wUbssUJkG5SSrnfm2g@mail.gmail.com \
    --to=martinwguy@gmail.com \
    --cc=ANDY.KENNEDY@adtran.com \
    --cc=crossgcc@sourceware.org \
    --cc=zmau1962@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).