#Hqplayer desktop software
Person or company who is being licensed to use the Software or Documentation. Versions, updates, additions and copies of the Software. "Software" includes any upgrades, modified The package contains software ("Software") and related explanatory written OF THIS AGREEMENT, CLICK THE "CANCEL" BUTTON, AND, IF APPLICABLE, UNINSTALL BY INSTALLING THE SOFTWARE ORĬLICKING ON THE "I AGREE" BUTTON, YOU ARE CONSENTING TO BE BOUND BY AND AREīECOMING A PARTY TO THIS AGREEMENT.
#Hqplayer desktop license
HQPlayer Desktop End User License AgreementĬAREFULLY READ THE FOLLOWING LICENSE AGREEMENT. The references hqplayer_3.11.0-31_bĬopyright: 1998-2015 Jussi Laako / Signalyst, How the rules are enforced and checked on a regular basis. That these packages are at least for more than a year inside the repository makes me wonder Who knows and can apply the rules of compliance to the packages in the repository. You maintain should be freezed and excluded from the repository as long someone I have to ask and request that you should be released from that task and that all software
The given PKGBUILD does not build any binary instead only copies the packaged binary from hqplayer_3.11.0-31_b. Binaries are generally not accepted and by far not without sources. Rules of Submission and referencing packaging standards make clear that the sources should be also availableĪnd they are the basis for the commonly required build.
Its proprietary one and with the missing sources absolutely inacceptableĪnd breaking the community ground rule of free software.
See the license below, thats the one given and submited on the linux system. You must know that no sources and a explicitly proprietary has been provided. Let me make clear that you as a maintainer are responsible that your managed packaged adhere and comply with the communityĪnd ArchLinux philosophy and rules of package submission.Īnd its it looks really that intentionally these rules have been broken to for other software you maintain also.
0 kommentar(er)
