Re: libgit2 - a true git library

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nicolas Pitre <nico@xxxxxxx> writes:

> Depends.  Sure, I gave permission to copy some of my code for JGIT 
> because 1) JGIT is Java code in which I have little interest, 2) the 
> different license was justified by the nature of the JGIT project, and 
> 3) although no license convey this I asked for the C version of git to 
> remain the authoritative reference and that any improvements done to JGIT 
> first be usable in the C version under the GPL.

This reminds me that Shawn earlier in an unrelated thread asked me if I
can relicense builtin-blame.c for JGIT; your reasoning fully matches that
of mine regarding that part of the code.

> My favorite license for a library is the GPL with the gcc exception,
> i.e. what libraries coming with gcc are using.  They're GPL but with an 
> exception allowing them to be linked with anything.

Although I'd be Ok with either GPL + gcc exception on whatever core-ish
(i.e. what will be necessary for libgit2; "blame" would not count) pieces
I have in C-git codebase, "can be linked with anything" allows a gaping
hole to the library, which I'm a bit hesitant to swallow without thinking.

E.g.  our read_object() may look like this:

         void *read_object(const object_name_t sha1,
                           enum object_type *type,
                           size_t *size)
         {
                 ...
         }


but an extension a closed-source person may sell you back may do:

        +typedef void *read_object_fn(const object_name_t,
        +                             enum object_type *,
        +                             size_t *);
        +read_object_fn read_object_custom = NULL;
         void *read_object(const object_name_t sha1,
                           enum object_type *type,
                           size_t *size)
         {
        +       if (read_object_custom != NULL)
        +               return read_object_custom(sha1, type, size);
                ...
         }

I.e. use the supplied custom function to do proprietary magic, such as
reading the object lazily from elsewhere over the network.  And we will
never get that magic bit back.

Although no license asks this, my wish is that if somebody built on top of
what I wrote to make the world a better place, I'd like the same access to
that additional code so that I too can enjoy the improved world.  Because
almost all of my code in git.git are under GPLv2, in reality I do not have
any access to your software as long as you do not distribute your
additional code that made the world a better place, which is a bit sad.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux