All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
To: "Jakub Narębski" <jnareb@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: Mon, 18 Jul 2022 17:08:02 +0530	[thread overview]
Message-ID: <CAPOJW5xR-MBU74h2mM3wENf_XjU-xm6n7qis0FLjFxZsUHsHAQ@mail.gmail.com> (raw)
In-Reply-To: <85r12iu10e.fsf@gmail.com>

On Mon, Jul 18, 2022 at 4:43 PM Jakub Narębski <jnareb@gmail.com> wrote:
>
> Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com> writes:
>
> > Hello,
> >
> > I need the CRoaring[1] library to use roaring bitmaps. But it has
> > Apache license v2 which is not compatible with GPLv2[2].
>
> Actually Apache License v2.0 *is* compatibile with GPLv2 and GPLv3
> in the sense that you can include the Apache licensed code (like the
> CRoaring library) in the GPLv2 project (like Git).
>
> Quote from the cited "Apache License V2.0 and GPL Compatibility"[2]:
>
>   The Free Software Foundation considers the Apache License, Version 2.0
>   to be a free software license, compatible with version 3 of the GPL.
>   The Software Freedom Law Center provides practical advice for
>   developers about including permissively licensed source.
>
>   Apache 2 software can therefore be included in GPLv3 projects, because
>   the GPLv3 license accepts our software into GPLv3 works. However,
>   GPLv3 software cannot be included in Apache projects. The licenses are
>   incompatible in one direction only, and it is a result of ASF's
>   licensing philosophy and the GPLv3 authors' interpretation of
>   copyright law.

But the same article also says  -

  Despite our best efforts, the FSF has never considered the Apache License
  to be compatible with GPL version 2, citing the patent termination
and indemnification
  provisions as restrictions not present in the older GPL license. The
Apache Software
  Foundation believes that you should always try to obey the
constraints expressed by
  the copyright holder when redistributing their work.

  reply	other threads:[~2022-07-18 11:38 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=CAPOJW5xR-MBU74h2mM3wENf_XjU-xm6n7qis0FLjFxZsUHsHAQ@mail.gmail.com \
    --to=chakrabortyabhradeep79@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.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.
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.