-
Notifications
You must be signed in to change notification settings - Fork 29
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
Possible license violation #11
Comments
This issue is a license violation, closing |
See #12 |
So in effect the comments of 811bc18 are null and void? |
No, it is not. Read it again. Project licence was upgraded to GPLv3 to be compatible with projects under Apache Licence 2.0. |
You have provided various provisions attempting to block people such as myself from using |
If your only purpose is to send rubbishy and pointless patches and issues for this project then sorry, I'm not going to discuss with you. Patch in this issue including your comments is just such spam example. |
It's actually a fairly serious concern, you either have or haven't blocked the use of |
Sorry, that is not my problem. They had more than half of year of time to resolve this issue. But that they did anything and just blaming me and other people. And I do not understand why you are reporting this issue to this project. It is problem in freedesktop, so once they fix it, we can continue here. |
You provide a pkg-config file, as pkg-config is a freedesktop project anyone using that file would be breaking your terms Aditionally Collabora have contributed to glibc and the kernel violating "loaded or linked at compile time or at runtime This particular problem cannot be resolved elsewhere as it is you who set these terms |
Could you please stop spamming this issue tracker? I have already expressed that I'm not interested in your rubbishy and pointless patches. To your previous comment, this repository does not contain any pkg config application nor any link to such application. And if you are unhappy that And if you do not like this library or you cannot use it then solution is simple: do not use it. I'm not forcing you to use it. This is my last comment in this nonsense topic. |
This is entirely unreasonable, this would prevent people from engaging in any development on systems where Given there is no compliant way to use that file (and it's existance effectively nukes pkg-config) it seems entirely sensible for it to be dropped |
@ZanderBrown actually, So, actually, there is no issue you mention. |
libopenaptx
provides a pkg-config file, assuming this file is distributed under the same terms as the rest oflibopenaptx
this breakslibopenaptx
license provisions around freedesktop projects (or rather could cause users to unintentionally break them)This can be resolved with the following patch
Unfortunately this patch cannot be contributed, even if I wanted to, since
libopenaptx
's license bars me from contributingAdditionally it should probably be made clear that uses of
libopenaptx
wishing to use glibc should use a version prior to at least bminor/glibc@a64afc2 (though I suspect to collabora involvement goes back further)The text was updated successfully, but these errors were encountered: