From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Taylor Blau <me@ttaylorr.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: Can I use CRoaring library in Git?
Date: Sat, 16 Jul 2022 16:16:26 +0200 [thread overview]
Message-ID: <220716.86y1wtxhok.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <CAPOJW5x4McofC5fxBvsRAzum28wmeDJCMTMRmY_0oy=32JjKqQ@mail.gmail.com>
On Sat, Jul 16 2022, Abhradeep Chakraborty wrote:
> Hello,
>
> I need the CRoaring[1] library to use roaring bitmaps. But it has
> Apache license v2 which is not compatible with GPLv2[2].
>
> Is there a way to use the CRoaring library in Git? Taylor told me that
> contrib/persistent-https tree is also licensed under Apache License
> version 2.
>
> [1] https://github.com/RoaringBitmap/CRoaring
> [2] https://www.apache.org/licenses/GPL-compatibility.html
As a replacement for git's own bitmap implementation?
It's one thing to have differently licensed code in-tree that's built as
a separate utility (like that persistent-https tool), but another if
this is going to be something linked to git itself.
My understanding is that such a thing could not be legally distributed
as a binary (e.g. by Debian et al), so the users will be limited to
those willing to build the two pieces from scratch locally, i.e. similar
to ZFS on Linux (which I think is still the state of that ...).
But I'm not a lawyer and all that.
Another possibility is to get the library to dual-license itself,
running "git shortlog -sn" on it it seems it's mainly written by one
contributor, with a relatively short tail of others, perhaps they'd be
willing to dual-license at the prospect of having git use it?
next prev parent reply other threads:[~2022-07-16 14:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 13:50 Can I use CRoaring library in Git? Abhradeep Chakraborty
2022-07-16 14:16 ` Ævar Arnfjörð Bjarmason [this message]
2022-07-16 16:26 ` Abhradeep Chakraborty
2022-07-17 12:25 ` Kaartic Sivaraam
2022-07-17 22:00 ` Junio C Hamano
2022-07-17 22:25 ` Taylor Blau
2022-07-18 8:57 ` Abhradeep Chakraborty
2022-07-25 22:11 ` Taylor Blau
2022-07-17 14:43 ` Derrick Stolee
2022-07-18 11:13 ` Jakub Narębski
2022-07-18 11:38 ` Abhradeep Chakraborty
2022-07-18 13:38 ` Ævar Arnfjörð Bjarmason
2022-07-18 11:48 ` Abhradeep Chakraborty
2022-07-18 12:18 ` Derrick Stolee
2022-07-18 13:15 ` Abhradeep Chakraborty
2022-07-18 21:48 ` brian m. carlson
2022-07-25 22:14 ` Taylor Blau
2022-07-25 22:35 ` rsbecker
2022-07-25 23:37 ` Taylor Blau
2022-07-21 4:07 ` Abhradeep Chakraborty
2022-07-21 6:12 ` Junio C Hamano
2022-07-21 12:14 ` Derrick Stolee
2022-07-21 13:51 ` Ævar Arnfjörð Bjarmason
2022-07-21 14:57 ` Abhradeep Chakraborty
2022-07-22 11:07 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=220716.86y1wtxhok.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=chakrabortyabhradeep79@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).