Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F-Droid inclusion #6

Open
AleixDev opened this issue Aug 9, 2014 · 7 comments
Open

F-Droid inclusion #6

AleixDev opened this issue Aug 9, 2014 · 7 comments

Comments

@AleixDev
Copy link

AleixDev commented Aug 9, 2014

Hi, I've tried to submit your application to F-Droid [a free (as in freedom) software repository] but it seems that there are a couple of questions that have to be solved before it can be added:

A couple of comments:

  • What is the jar libs/dd-plist.jar?
  • You cannot use GPLv2 with support-v4, since it's Apache2 and those two are incompatible.

Is the library "dd-plist.jar" the same as the one which can be found here?

@mvdan
Copy link

mvdan commented Aug 9, 2014

The main issue with dd-plist.jar is that we don't know what version of the library that is.

@HexAirbot, if you could use that library from source, that'd be much better.

@HexAirbot
Copy link
Owner

dd-plist.jar is used to analyze Apple plis t file,a kind of key-value file. dd-plist.jar was added to the project a year ago, and we forget the version chosed.
Maybe some code are not under GPLv2, thank you for let we known that, we will adjust the content later.

@ligi
Copy link

ligi commented Aug 12, 2014

you could switch to GPLv3 - the problem is only with GPLv2 http://www.apache.org/licenses/GPL-compatibility.html

@mvdan
Copy link

mvdan commented Aug 12, 2014

Yep, switching to GPLv3 or any other Apache2-compatible license will do it.

Regarding dd-plist.jar, we need to know what version it comes from. Maybe update to a newer version so that we know which one it is? It would be best if you used it from source, but a jar with the version name would be a starting point.

@ghost
Copy link

ghost commented Aug 14, 2014

  • License: everything has been said.
  • Plist: https://code.google.com/p/plist/ offers only two tagged releases, the last version should work -- if not the other one will mostlikely do.
  • Encoding: After working around those two issues, the build still fails as there are multiple encodings used. Starting with an iso-8859 dialect, utf-8 and utf-16. Could these be unified?

@HexAirbot
Copy link
Owner

License: we are considering changing the license to GPLv3, but now we are still confused about the differences between the GPL v2 and v3.
Plist: It will be nice the use the source code.
Encoding: The endoing of the project is GBK

@mvdan
Copy link

mvdan commented Aug 16, 2014

GBK? Why not just use UTF-8?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants