News for hackers. Stuff that matters.
Re:New implementation of Git in OCaml by avar on Saturday August 26, 2017 @09:36AM (#15105357)
This implementation is freely licenced enough that the BSDs and others that don't use Git for license reasons could use it.

It would be interesting to see an alternative implementation like this get enough feature parity that projects like the BSDs could migrate and still be protocol and worktree compatible so most users could continue using the GPL2 implementation.

Edit: Seems people here are unaware that the BSDs treat GPL software like cooties, see e.g. [1]. They wouldn't start using source control that gave them less freedom than SVN, an with CVS there's the expectation that OpenCVS might get finished.

1. https://wiki.freebsd.org/GPLinBase

Re:New implementation of Git in OCaml by SwellJoe on Saturday August 26, 2017 @08:51PM (#15108369)
"with CVS there's the expectation that OpenCVS might get finished."

Good lord. Surely, no one is working on reimplementing CVS in 2017?

The CVS repository (https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/cvs/) seems to actually have quite a bit of recent activity, so it seems to be a serious project that someone intends to deploy in the real world. There are a handful of things that the OpenBSD project does that I feel are quixotic (continuing to use CVS for everything, in general, is one of them), but this one takes the cake. CVS was good when compared to what came before (and in some regards even compared to Subversion), but there's no comparison with git (or any of the modern DVCS, really).

Re:New implementation of Git in OCaml by doozy on Saturday August 26, 2017 @11:18AM (#15105795)
Unfortunately OCaml itself has its own weird licensing issues being distributed under a combination of the QPL and GNU licenses.

Every few years I take a look at it, notice the license and move on. There's no reason whatsoever for a language not to have an implementation under a permissive license.

Re:New implementation of Git in OCaml by Drup on Saturday August 26, 2017 @12:56PM (#15106258)
The QPL is not used anymore. The OCaml compiler is GPL, the OCaml standard library is LGPL with the OCaml linking exception and the license of produced binaries is whatever the author wants.

If you still have issues with that .. I would really like an explanation.

Re:New implementation of Git in OCaml by xfer on Saturday August 26, 2017 @01:52PM (#15106526)
People just want reasons to complain about languages, see also: racket, when they have nothing to complain about they pick the license.
Re:New implementation of Git in OCaml by moron4hire on Saturday August 26, 2017 @02:59PM (#15106839)
No, there's no reason to avoid the GPL for languages, because you aren't building a derivative work of the language itself, so it's licensing has no bearing on your software.
Re:New implementation of Git in OCaml by steinuil on Saturday August 26, 2017 @03:48PM (#15107021)
That's not entirely true; GCC (and almost every other GPL-licensed compiler) has a specific exception for its runtime libraries that lets you distribute their compiled version under any license [1].

But for example, Ada Core's GNAT is licensed under GPL but doesn't have that exception, which makes the binaries it outputs be licensed under the GPL as well, to make you buy the Pro version of the compiler.

https://www.gnu.org/licenses/gcc-exception-faq.html

Re:New implementation of Git in OCaml by rjsw on Saturday August 26, 2017 @10:55AM (#15105702)
There isn't one single reason for avoiding use of GPL software that is true for all BSD variants.

Requiring OCaml in the base operating system could equally be a reason to avoid this, whatever licence is used.

Re:New implementation of Git in OCaml by throwawayjava on Saturday August 26, 2017 @11:12AM (#15105777)
> Requiring OCaml in the base operating system

I'm not sure I understand this concern in the majority use cases. Why would you need an OCaml compiler installed?

Re:New implementation of Git in OCaml by messe on Saturday August 26, 2017 @11:57AM (#15105975)
The base system is usually capable of compiling itself. If the source for your base system is stored on a remote git repository, and your implementation of git in your base system is written in OCaml, you're going to have to use an OCaml compiler to recompile it.
Re:New implementation of Git in OCaml by int_19h on Saturday August 26, 2017 @09:31PM (#15108527)
But you don't need source control to compile the base. You only need it to retrieve the base sources - and even then only when you want to get the latest, since the installer comes with a tarball of /usr/src.
Re:New implementation of Git in OCaml by gribbly on Saturday August 26, 2017 @09:50AM (#15105423)
Hmmm... in what way does Git being GPL/LGPL cause licence problems for the BSDs ?
Re:New implementation of Git in OCaml by teamhappy on Saturday August 26, 2017 @10:10AM (#15105515)
I guess you'd want to be able to include it in your distribution. FreeBSD for example includes svn (or svnlite or whatever) so you can fetch/update the source and do a buildkernel or buildworld without having to install any ports.
Re:New implementation of Git in OCaml by gribbly on Saturday August 26, 2017 @11:21AM (#15105810)
But you can include Git in the distribution, it's a self-contained program, it's license won't affect anything else it ships alongside with.
Re:New implementation of Git in OCaml by teamhappy on Saturday August 26, 2017 @11:47AM (#15105933)

    > The FreeBSD Project aims to produce a complete, 
    > BSD-licensed operating system allowing consumers of the
    > system to produce derivative products without constraint
    > or further license obligations.
https://www.freebsd.org/internal/software-license.html

Also https://www.openbsd.org/goals.html and https://www.netbsd.org/about/redistribution.html#why-berkele...

Re:New implementation of Git in OCaml by gribbly on Saturday August 26, 2017 @01:07PM (#15106293)
Ok, so it's license philosophy rather than any actual license legality problematics, I can understand that.
Re:New implementation of Git in OCaml by michaelmrose on Saturday August 26, 2017 @01:18PM (#15106345)
If someone wanted to produce a FreeBSD derivative would they really need to be able to ship a modified version of git?
Re:New implementation of Git in OCaml by loeg on Saturday August 26, 2017 @08:55PM (#15108393)
Suffice to say, FreeBSD's current stance on licensing is that new GPL2 software in base is unacceptable, and the goal is to get to no GPL2 software in base.
Re:New implementation of Git in OCaml by xyzzy_plugh on Saturday August 26, 2017 @04:53PM (#15107385)
Probably not, but then it wouldn't be "Free".
Re:New implementation of Git in OCaml by jlg23 on Saturday August 26, 2017 @12:09PM (#15106033)
It does affect the users' abilities to hack on the software. Since BSDs are used a lot in commercial environments this is a real concern for BSD-hackers.
Re:New implementation of Git in OCaml by k__ on Saturday August 26, 2017 @09:49AM (#15105416)
What's the problem with using GPL software if you don't want to change it?
Re:New implementation of Git in OCaml by yorwba on Saturday August 26, 2017 @10:12AM (#15105523)
AFAIK, software for the BSDs is usually maintained in-tree, and patched to integrate with the rest of the distribution. I don't think including GPL-licensed software would be compatible with the BSD license of the overall project. That doesn't mean you can't use anything GPL, just that it can't become part of the system.
Re:New implementation of Git in OCaml by _delirium on Saturday August 26, 2017 @12:10PM (#15106039)
All the BSDs have traditionally included GPL'd software in the base system, so I don't think many people share this view (it's a possible interpretation of the GPL, but not a common one). As one major example: every BSD until recently included gcc in-tree, and OpenBSD and NetBSD still do.
Re:New implementation of Git in OCaml by loeg on Saturday August 26, 2017 @08:57PM (#15108402)
FreeBSD sees this as a necessary evil and aims to move to zero GPL code in base, eventually (when ports GCC works well enough for 2nd tier architectures and Clang/ias / elftoolchain works well enough for 1st tier architectures).
Re:New implementation of Git in OCaml by int_19h on Saturday August 26, 2017 @09:33PM (#15108533)
Doesn't FreeBSD use Clang exclusively in the base system these days, and gcc from ports?
Re:New implementation of Git in OCaml by loeg on Saturday August 26, 2017 @09:41PM (#15108573)
On x86 and arm64, yeah. MIPS and Sparc still build with base GCC (4.2, last GPL2 version). I'm not sure what arm32 or ppc uses by default these days.
Re:New implementation of Git in OCaml by toast0 on Saturday August 26, 2017 @06:50PM (#15107901)
Who says they don't want to change it? Integration with OpenBSD pledge or FreeBSD capsicum could be useful.
Re:New implementation of Git in OCaml by user5994461 on Saturday August 26, 2017 @10:47AM (#15105663)
You can't use GPL code in non GPL software.
Re:New implementation of Git in OCaml by perlgeek on Saturday August 26, 2017 @10:52AM (#15105688)
I thought you can't link to GPL Software in non-GPL software?

Shipping an unmodified copy of git and calling it should be fine even in proprietary code, no?

Re:New implementation of Git in OCaml by wildmusings on Saturday August 26, 2017 @11:05AM (#15105749)
This is an open question. The GPL itself does not define what constitutes a derivative work. The FSF does, however, promote the view that linking does create a derivative work, while simply calling an external binary in usual cases does not. But that can't function as a hard rule. Because I could just make a wrapper binary that handles all of the scenarios I need a GPL'd library for, and then call my wrapper executable from my proprietary code.
Re:New implementation of Git in OCaml by jahewson on Saturday August 26, 2017 @11:43AM (#15105920)
> Because I could just make a wrapper binary that handles all of the scenarios I need a GPL'd library for, and then call my wrapper executable from my proprietary code.

Yes, you can literally do this. It's not a derived work because your code is entirely independent of the GPL'd code and the GPL can't possibly cover code that you wrote independently. Simply interacting with some external GPL'd program does not expose your code to any GPL requirements.

Re:New implementation of Git in OCaml by wildmusings on Saturday August 26, 2017 @11:52AM (#15105952)
You can't just work around the GPL by placing a command-line interface as a shim between your code and the function call interface of the GPL'd library. I'm talking about a contrived binary that just calls library functions, forwarding command line parameters to the arguments of that function as necessary.
Re:New implementation of Git in OCaml by jahewson on Saturday August 26, 2017 @12:06PM (#15106013)
Oh yes you can. The GPL gets its power from copyright - the rights that the authors of the original software have over their work. It does not and cannot place any restrictions on any software that you write, unless you literally incorporate the GPL'd source or binary into your software, which a CLI interface does not. The same would be true of an RPC interface.

For example, many databases are GPL'd and provide their entire functionality over RPC. Many CLI programs are GPL'd and (of course) provide their entire functionality over CLI. Neither of these cases place GPL obligations on clients, and it's no different for any given library which you wrap with a CLI.

Re:New implementation of Git in OCaml by wildmusings on Saturday August 26, 2017 @12:30PM (#15106146)
The FSF disagrees with you. https://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySy...

A contrived wrapper that is not an independently useful program does not allow you to circumvent the GPL.

You are leaning very heavily on a technical distinction (linking vs. not linking) instead of on a holistic analysis of what a "derived work" is.

Re:New implementation of Git in OCaml by zokier on Saturday August 26, 2017 @01:24PM (#15106374)
FSF is neither authoritative nor unbiased source for answer to this question. I'd like to see few court cases that have gone through the motions before thinking this subject to be settled.
Re:New implementation of Git in OCaml by michaelmrose on Saturday August 26, 2017 @01:21PM (#15106358)
Pretty sure the FSF can't magically extend what copyright means to comport with what they think it ought to mean in regard to free software.
Re:New implementation of Git in OCaml by adament on Saturday August 26, 2017 @02:12PM (#15106603)
Now I am not a lawyer, but I think by analogy the FSFs interpretation would also be needed to enforce the CreativeCommons NoDerivatives licenses. Imagine someone creates an interview-based documentary video series on a controversial scientific topic say global warming and releases it under a NoDerivatives license because they are afraid that a clever edit of their videos would present the topic incorrectly and they have made promises to the scientists about how they will and will not present them.

Now imagine that I rather than edit the video files themself create a playlist, in a (fictive?) format which has the ability to play subsequences of the linked files, and then creates a version of the series which presents the complete opposite message of the original. Would a court find this to be a derivative work of the original videos? What if in my need to edit the video I want to insert certain new short sequences, and thus I distribute a second video along with the playlist, but this video is useless in itself since it just contains a number of short clips in sequence. Would this video be considered a derivative work of the original - remember it serves no purpose in itself except along with the playlist and the original? To me it is not clear, but if they are not derivatives, then this will practically render the concept moot. Since most derivatives could potentially be formulated as the original + a diff. Now I would expect in this case that the combination of the playlist + my video file + original series be considered a derivative work, remember that in the arts transferring a work from one format to another (a dramatization for example) is considered to be a derivative work, even if all the actors would be seen on stage to read from the original book.

As I read it, this is the center of the FSFs argument. Now whether this would apply equally to software I do not know. But I have a hard time imagining that copyright is not as easily circumvented as you seem to indicate.

Re:New implementation of Git in OCaml by jahewson on Saturday August 26, 2017 @07:27PM (#15108042)
That's a great question. Would this be a derivative work? I suspect the answer is yes, because in your scenario you've effectively shipped a piece of software which creates a derivative work on-the-fly. I guess it's sort of like an analogy of dynamic linking.
Re:New implementation of Git in OCaml by jononor on Saturday August 26, 2017 @07:49PM (#15108118)
The default in copyright is that you have no rights to a copyrightable work. The GPL grants you some right under certain conditions. If the conditions fail to be met, your granted rights are revoked. As the creators of the GPL license the FSFs widely published opinion is likely to matter to judges evaluating a case. But in the end noone knows outcomes until would come to pass. So seek to minimize legal risks.
Re:New implementation of Git in OCaml by jahewson on Saturday August 26, 2017 @09:32PM (#15108532)
Your comment is literally FUD. Copyright law gives the authors of the GPL'd work exactly no rights over your independent work. Distributing a GPL'd binary along side other works cannot have any impact on those other works. (Otherwise every Linux distribution would be in violation). The GPL is built on top of existing copyright laws which simply don't provide that kind of power. So there is no risk because there's no conceivable legal mechanism in copyright law which behaves like you claim.
Re:New implementation of Git in OCaml by jononor on Sunday August 27, 2017 @05:55AM (#15110029)
I meant rights to the GPLed software/library in use. Not to independent works merely aggregated on the same medium.
Re:New implementation of Git in OCaml by michaelmrose on Saturday August 26, 2017 @01:19PM (#15106355)
Can you substantiate that claim?
Re:New implementation of Git in OCaml by lomnakkus on Saturday August 26, 2017 @07:30PM (#15108048)
What claim?

I think it's pretty obvious that the GPL derives it's power from copyright. Reasoning: If the GPL does not apply, then you don't have any right to anybody else's code (by the Berne Convention), so it gets its power by granting you more rights than you would have had by default. Make sense?

Re:New implementation of Git in OCaml by loeg on Saturday August 26, 2017 @08:53PM (#15108382)
It might be easier to just write a permissively licensed 'gitlite' that can checkout sources (and maybe even update a clean tree). That is the potential solution I've heard discussed in BSD land.