From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: makemkv-1.17.1
Date: Sun, 07 Aug 2022 12:51:20 +0200 [thread overview]
Message-ID: <20220807105120.DYFFl65E_nUMjcQV7_G-y_wCKzFXXMyYOpCkpS6h8Nk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27960@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/27960#issuecomment-1207350231
Comment:
> Isn't bundling GPL jar and proprietary binaries a GPL breach?
<del>maybe? IANAL, but it's at least a bit fishy IMO.</del> I think it might be fine actually, but I'd need to check more into what code comes from where and who holds the copyright and such. In general, taking GPL code and building something proprietary based on it is a breach, but I don't think that's happening here. I think they are dual-licensing some parts under both their proprietary license and under the GPL, but keeping some core things to themselves which are only released under the proprietary license. If they are indeed shipping GPL code for which they have no copyright in binaries for which they don't release the full source code under the GPL, then that would be a breach, yes.
Still, I don't see any harm in shipping this as a package in non-free, right? It's being shipped by a few other distros as well, see https://repology.org/project/makemkv/versions
next prev parent reply other threads:[~2022-08-07 10:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 23:42 [PR PATCH] New package: makemkv-1.15.4 jcgruenhage
2021-01-15 23:59 ` [PR PATCH] [Updated] " jcgruenhage
2021-01-18 17:44 ` Chocimier
2021-01-19 0:16 ` jcgruenhage
2021-01-19 13:16 ` [PR PATCH] [Updated] " jcgruenhage
2021-06-21 10:09 ` [PR REVIEW] " jcgruenhage
2022-05-02 2:16 ` github-actions
2022-05-03 9:06 ` [PR PATCH] [Updated] " jcgruenhage
2022-05-03 9:07 ` jcgruenhage
2022-05-03 9:20 ` jcgruenhage
2022-05-07 21:59 ` Piraty
2022-05-07 22:07 ` Chocimier
2022-08-07 2:13 ` github-actions
2022-08-07 7:39 ` jcgruenhage
2022-08-07 7:40 ` [PR PATCH] [Updated] " jcgruenhage
2022-08-07 10:51 ` jcgruenhage [this message]
2022-11-07 2:12 ` New package: makemkv-1.17.1 github-actions
2022-11-14 9:37 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-14 9:37 ` jcgruenhage
2023-01-22 1:46 ` New package: makemkv-1.17.2 agausmann
2023-01-27 1:01 ` agausmann
2023-04-27 1:52 ` github-actions
2023-05-03 18:46 ` jcgruenhage
2023-08-03 1:48 ` github-actions
2023-08-03 18:39 ` Chocimier
2023-08-03 18:46 ` Chocimier
2023-11-03 1:45 ` github-actions
2023-11-17 1:46 ` [PR PATCH] [Closed]: " github-actions
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=20220807105120.DYFFl65E_nUMjcQV7_G-y_wCKzFXXMyYOpCkpS6h8Nk@z \
--to=jcgruenhage@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).