From: iFoundSilentHouse <iFoundSilentHouse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Helio Sequencer
Date: Fri, 22 Mar 2024 19:17:41 +0100 [thread overview]
Message-ID: <20240322181741.8726F2158C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48957@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
New comment by iFoundSilentHouse on void-packages repository
https://github.com/void-linux/void-packages/issues/48957#issuecomment-2015662631
Comment:
> @iFoundSilentHouse Why does it not suit the BSD license of Void? Packages distributed by void don't have to be BSD or MIT. In this case, it is clearly dual licensed.
>
> Anyways, a template is nice, thanks.
As far as I can understand, helio-sequencer uses JUCE packages X. When someone installs JUCE packages X, he agrees to distribute his program under under gpl. Xbps is a compiling-based package manager - it needs to download them. And it's bsd licensed. Bsd claims that it can close source once needed. This hypothetical action will violate JUCE license and cause court proceedings
next prev parent reply other threads:[~2024-03-22 18:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 23:12 [ISSUE] " blacklightpy
2024-03-18 20:41 ` iFoundSilentHouse
2024-03-18 20:42 ` iFoundSilentHouse
2024-03-22 16:15 ` iFoundSilentHouse
2024-03-22 16:16 ` iFoundSilentHouse
2024-03-22 16:23 ` blacklightpy
2024-03-22 16:23 ` blacklightpy
2024-03-22 16:25 ` blacklightpy
2024-03-22 16:30 ` iFoundSilentHouse
2024-03-22 18:17 ` iFoundSilentHouse [this message]
2024-03-26 22:39 ` blacklightpy
2024-03-26 22:40 ` blacklightpy
2024-03-27 4:08 ` iFoundSilentHouse
2024-03-27 15:10 ` blacklightpy
2024-03-27 15:11 ` blacklightpy
2024-03-28 15:31 ` blacklightpy
2024-03-28 15:32 ` blacklightpy
2024-03-28 15:55 ` iFoundSilentHouse
2024-03-28 15:56 ` iFoundSilentHouse
2024-03-28 16:41 ` blacklightpy
2024-03-28 17:07 ` classabbyamp
2024-03-28 17:21 ` iFoundSilentHouse
2024-03-28 17:24 ` iFoundSilentHouse
2024-03-28 17:25 ` iFoundSilentHouse
2024-03-28 17:28 ` classabbyamp
2024-03-28 17:41 ` iFoundSilentHouse
2024-03-28 17:45 ` blacklightpy
2024-03-28 17:47 ` blacklightpy
2024-03-28 17:47 ` blacklightpy
2024-03-28 18:13 ` blacklightpy
2024-03-28 18:13 ` blacklightpy
2024-03-28 18:24 ` iFoundSilentHouse
2024-03-28 18:31 ` blacklightpy
2024-05-09 10:04 ` 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=20240322181741.8726F2158C@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).