All of lore.kernel.org
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Daniel Searles <dsearles@medialab.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Drew Northup <drew.northup@maine.edu>,
	Joshua Juran <jjuran@gmail.com>,
	git@vger.kernel.org, oleganza@gmail.com,
	Chris Perkins <cperkins@medialab.com>
Subject: Re: Gitbox
Date: Wed, 13 Apr 2011 15:13:44 -0700	[thread overview]
Message-ID: <86hba1hk9z.fsf@red.stonehenge.com> (raw)
In-Reply-To: <1C18B4FB-BB10-4AC7-8952-D477CB4EF289@medialab.com> (Daniel Searles's message of "Wed, 13 Apr 2011 14:56:15 -0700")

>>>>> "Daniel" == Daniel Searles <dsearles@medialab.com> writes:

Daniel> It seems to me that since gitbox is useless without git it is
Daniel> definitely in violation of the GPL. My interpretation of the GPL
Daniel> is based off of the following article:
Daniel> http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/doc/Why-CLISP-is-under-GPL

And note the author of that opinion, RMS, who would always rule in favor
of more things needing to be under the GPL as the One True License.

And it's also about readline.a, which *has* to be linked into a binary
to make it work.  None of the git code is being *linked* in.

Particularly, I see this phrase in the actual license of Git (version 2,
not version 3 under which Readline is distributed):

    Thus, it is not the intent of this section to claim rights or contest
    your rights to work written entirely by you; rather, the intent is to
    exercise the right to control the distribution of derivative or
    collective works based on the Program.

    In addition, mere aggregation of another work not based on the Program
    with the Program (or with a work based on the Program) on a volume of
    a storage or distribution medium does not bring the other work under
    the scope of this License.

I'd consider the git binary distribution to be an aggregation with
gitbox, not a "linking", presuming that one of the following has also
happened:

      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) Accompany it with the information you received as to the offer
        to distribute corresponding source code.  (This alternative is
        allowed only for noncommercial distribution and only if you
        received the program in object code or executable form with such
        an offer, in accord with Subsection b above.)

I cannot confirm that one of these has been done, but let's say it has.

As already said in this thread, if "execve()" is considered a "linking",
then *everything* in a typical Linux distro would *have* to be GPL.
That's patently not the case.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion

  parent reply	other threads:[~2011-04-13 22:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 18:16 Gitbox Daniel Searles
2011-04-13 18:55 ` Gitbox Joshua Juran
2011-04-13 18:59 ` Gitbox Drew Northup
2011-04-13 19:09   ` Gitbox Joshua Juran
2011-04-13 19:16     ` Gitbox Drew Northup
2011-04-13 19:24       ` Gitbox Joshua Juran
2011-04-13 19:41       ` Gitbox Randal L. Schwartz
2011-04-13 20:04         ` Gitbox Drew Northup
2011-04-13 20:26           ` Gitbox Taylor Hedberg
2011-04-13 20:29           ` Gitbox Joshua Juran
2011-04-13 22:56           ` Gitbox Tim Smith
2011-04-14  9:52           ` Gitbox Sitaram Chamarty
2011-04-14 10:03             ` Gitbox Vincent van Ravesteijn
2011-04-14 12:34             ` Gitbox Drew Northup
2011-04-13 20:43         ` Gitbox Junio C Hamano
     [not found]           ` <1C18B4FB-BB10-4AC7-8952-D477CB4EF289@medialab.com>
2011-04-13 22:13             ` Randal L. Schwartz [this message]
2011-04-13 23:10           ` Gitbox Randal L. Schwartz
2011-04-13 19:18 ` Gitbox Jakub Narebski
     [not found] <BANLkTikfCDm-5Yde=2Cm-ROc1dcMwopvOg@mail.gmail.com>
2011-04-13 22:23 ` Gitbox Joshua Juran
2011-04-14  1:58   ` Gitbox Chris Perkins
2011-04-14  2:02     ` Gitbox Randal L. Schwartz
2011-04-14  2:28     ` Gitbox Chris Perkins
2011-04-14  2:34       ` Gitbox Randal L. Schwartz
2011-04-14  4:59       ` Gitbox Joshua Juran
2011-04-14 13:55     ` Gitbox Martin Langhoff
     [not found]     ` <32803572.1897.1302789371873.JavaMail.trustmail@mail1.terreactive.ch>
2011-04-14 14:15       ` Gitbox Victor Engmark
2011-04-14 14:52         ` Gitbox Martin Langhoff
2011-04-15 19:21     ` Gitbox Tim Smith

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=86hba1hk9z.fsf@red.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=cperkins@medialab.com \
    --cc=drew.northup@maine.edu \
    --cc=dsearles@medialab.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jjuran@gmail.com \
    --cc=oleganza@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.