On Wed, Aug 06, 2014 at 02:10:08PM -0400, Robert P Fischer wrote:
> I ran git on my newly-set-up OS X Mavericks machine, and get:
> $ git
> Agreeing to the Xcode/iOS license requires admin privileges,
> please re-run as root via sudo.
> Running 'git --verision' gives the same result. This seems
> problematic in a few ways, and I am wondering if the git community is
> interested in addressing it:
> 1. Why do I have to agree to Apple's licensing terms to use an LGPL
> program? Is this appropriate? Is it allowed under the LGPL?
You are not running the real "git" at all here; Apple ships stubs for
several commands, including git, that are distributed with XCode. When
you run the program, it prompts you to install XCode, which then
actually downloads and installs git, replacing the stub.
You can download XCode separately, of course, but you would still need
to agree to the license. You can download git separately and not need to
bother (though I do not know offhand how to download Apple's git, or
whether they provide a script to replace the stubs).
Also, minor nit, but git is GPL, not LGPL.
> 2. This is a significant problem for me, because I'm using a work
> machine and do not have admin access.
You can always download and install git yourself. There's no need to use
the XCode version. However, XCode is the simplest way to get a compiler
on the machine, AFAIK (I do not use OS X myself).
> 3. The version of git I ran is clearly NOT a plain vanilla "official"
> git, it is a derivative work. Has Apple provided the source code of
> the special version that I just ran? If not, that would seem to be a
> violation of the LGPL.
You didn't run a derivative git. You ran their stub.
As it happens, though, they _do_ modify the git that they distribute. I
know at least that they bake-in the osxkeychain helper config in away
that the user cannot turn off. There may be more changes, but I haven't
done a full diff. And they do provide the source:
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html