kala-tamin How to distribute slightly modified GPL python library that's abandoned? [closed]


How to distribute slightly modified GPL python library that's abandoned? [closed]



My apologies if this question has been asked.

I have made a bug fix in a small python library. This particular library is licensed under GPL but the development of it seems to be dead and abandoned (very low activity on their tracker, to which I have attached my patch).

I'm developing a python application which uses this library. What is the proper way to distribute it along with my patched version of the library?




Subsonic 3 Linq Projection Issue

1:



Linq (MIN && MAX)
Whether the library is abandoned or not, if you use it, then your code (both patched library and application) must be distributed under the GPL too, assuming you want to distribute it at all..
Using Linq SubmitChanges without TimeStamp and StoredProcedures the same time


where to find a small example/demo on how to create a LINQ Provider?


SubSonic 3 ActiveRecord lambda expression partially ignored on delete

2:



Trouble with a LINQ 'filter' code throwing an error
Your patched library is GPL for sure and most likely so is your application.


Can't insert data in a table using entity framework
If you're fine with that, then there's no problem.


How do you return a default value if a LINQ to entities query returns no values
If you would like to use a different license with your application, it depends how you want to understand what GPL means by "derived work".. If your application does not depend much on the library (you did say it's a small library) and there are other (non-GPL) libraries doing the same thing that you could just as well use (or the user of the application could use), then...

well ...

you might not need to license the app under GPL, mostly because it is arguable that doesn't really derive from that library.

But that's really loose definition.. If the library was LGPL, then you could license your app which way you wanted, but your patched library would be under LGPL.

And because the original authors of the library chose GPL instead of LGPL, it can be assumed that they wanted the apps using their library also be under GPL.

This is the usual counterargument to the view in the previous paragraph.. Of course, you can also ask the authors of the original library if they grant you license to the library with more permissive license (like LGPL)..


3:


Agree with the reply from Anon, your code (both patched library and application) must be distributed under the GPL too.. You can lookup GPL v2.0 requirements here:. https://enterprise.dejacode.com/license_library/Demo/gpl-2.0/#license-requirements. Hope it helps..



93 out of 100 based on 73 user ratings 1173 reviews