-
Notifications
You must be signed in to change notification settings - Fork 25
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
License inconsistency between sources and COPYING #9
Comments
And then if any header files etc miss the license header?
@nkoriyama , while I'm 100% OK with the v3+ requirement if that's the license of the overall work, I would prefer it to be normalized or specified so as to minimize questions like this (to whichever side is the actual license of the combined work). After that a 1.0.4 release could be carved so that LGPL usage could be added to projects. Right now it is not possible to differentiate between a GPL-only version of aribb24 and an LGPL+ version of aribb24 by the version number in the pc file. プロジェクト全体のライセンスがLGPLv3+であればこういう質問を防ぐためにも一応READMEなどにて明確に表記しておいた方がいいでしょう。「プロジェクト全体のソースファイルがLGPL2.1+ヘッダ付きであっても、このプロジェクトのライセンスはLGPLv3+である」とか。でなければLGPLv2.1+で使いたがる人がかならず出てきて、このような質問を出してくる(と思ふ)。あと、プロジェクトがLGPL系になってからは一度もリリースが出ていないみたいので1.0.4リリースがあればpkg-configでLGPLなバージョンに限定できるようになりますので、できればお願い致します。 |
Maybe we should fork that project on code.videolan.org. |
The COPYING file is LGPL-3.0. However, the source files seem to have:
Could you please clarify whether '2.1 or newer' is correct (e.g. in README)?
The text was updated successfully, but these errors were encountered: