Github messages for voidlinux
 help / color / mirror / Atom feed
From: iFoundSilentHouse <iFoundSilentHouse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: helio-sequencer-3.12
Date: Wed, 20 Mar 2024 07:07:15 +0100	[thread overview]
Message-ID: <20240320060715.61FD22019D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49361@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

New comment by iFoundSilentHouse on void-packages repository

https://github.com/void-linux/void-packages/pull/49361#issuecomment-2008712815

Comment:
ahesford, I read through licence of JUCE and it's not that bad to even mark h-s as nonfree: 
```
Once your business hits the Revenue Limit for your JUCE license tier, to continue distributing your Applications you will either have to upgrade your JUCE license, or instead release your Applications under the [GNU General Public License v.3](https://www.gnu.org/licenses/gpl-3.0.en.html), which means, amongst other things, that you must make the source code of your Applications available.
```
And in end-user agreement:
```
1.9. Remember, unless you upgrade to JUCE Indie or JUCE Pro, if you exceed the Revenue Limit for JUCE Personal and you want to continue distributing Applications, then you must do so under the GNU GPLv3 License. The GNU GPLv3 is an open-source licence and requires, among other things, that you make your source code available and license modified files and larger derived works (including all linked code) under the same terms of the GNU License. Please review the terms of the GNU GPLv3 License carefully.
```
It's like... forced GPL but not forced payment or anything like that
Though of course i agree on that this wierd licence should be installed

  parent reply	other threads:[~2024-03-20  6:07 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 20:18 [PR PATCH] " iFoundSilentHouse
2024-03-18 20:26 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-18 20:31 ` iFoundSilentHouse
2024-03-18 20:37 ` iFoundSilentHouse
2024-03-18 20:40 ` iFoundSilentHouse
2024-03-18 20:50 ` iFoundSilentHouse
2024-03-19 12:36 ` [PR REVIEW] " ahesford
2024-03-19 12:36 ` ahesford
2024-03-19 12:36 ` ahesford
2024-03-19 12:36 ` ahesford
2024-03-19 12:36 ` ahesford
2024-03-19 12:36 ` ahesford
2024-03-19 13:15 ` iFoundSilentHouse
2024-03-19 13:25 ` iFoundSilentHouse
2024-03-19 13:26 ` iFoundSilentHouse
2024-03-19 13:27 ` iFoundSilentHouse
2024-03-19 13:28 ` iFoundSilentHouse
2024-03-19 13:29 ` iFoundSilentHouse
2024-03-19 13:32 ` ahesford
2024-03-19 13:34 ` ahesford
2024-03-19 13:36 ` ahesford
2024-03-19 13:37 ` ahesford
2024-03-19 14:13 ` iFoundSilentHouse
2024-03-19 14:20 ` ahesford
2024-03-19 14:30 ` [PR PATCH] [Closed]: " iFoundSilentHouse
2024-03-19 18:58 ` [PR REVIEW] " meator
2024-03-19 21:04 ` iFoundSilentHouse
2024-03-19 21:12 ` meator
2024-03-19 21:38 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-19 21:42 ` [PR REVIEW] " meator
2024-03-19 21:44 ` meator
2024-03-19 21:53 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-19 22:01 ` iFoundSilentHouse
2024-03-20  0:15 ` iFoundSilentHouse
2024-03-20  0:24 ` iFoundSilentHouse
2024-03-20  5:17 ` iFoundSilentHouse
2024-03-20  5:27 ` iFoundSilentHouse
2024-03-20  5:28 ` iFoundSilentHouse
2024-03-20  5:32 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-20  5:39 ` ahesford
2024-03-20  5:47 ` ahesford
2024-03-20  5:55 ` iFoundSilentHouse
2024-03-20  6:07 ` iFoundSilentHouse [this message]
2024-03-20  6:19 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-20  6:32 ` iFoundSilentHouse
2024-03-20  6:57 ` iFoundSilentHouse
2024-03-20  7:18 ` iFoundSilentHouse
2024-03-20  7:19 ` iFoundSilentHouse
2024-03-20  8:16 ` gmbeard
2024-03-20 11:32 ` ahesford
2024-03-20 11:52 ` iFoundSilentHouse
2024-03-20 12:12 ` [PR PATCH] [Closed]: " ahesford
2024-03-20 12:12 ` ahesford
2024-03-20 14:16 ` Johnnynator
2024-03-20 14:18 ` Johnnynator
2024-03-20 18:29 ` ahesford
2024-03-22  1:27 ` blacklightpy
2024-03-23 21:53 ` [PR REVIEW] " meator
2024-03-28 15:47 ` blacklightpy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240320060715.61FD22019D@inbox.vuxu.org \
    --to=ifoundsilenthouse@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).