From: 2asoft <2asoft@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: Jetbrains IDEs
Date: Tue, 29 Sep 2020 06:51:49 +0200 [thread overview]
Message-ID: <20200929045149.g5axYGYyEv3qu_GuPcWv_lstpNF9Y1sU3tMpqkQDdV8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-9299@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
New comment by 2asoft on void-packages repository
https://github.com/void-linux/void-packages/issues/9299#issuecomment-699723085
Comment:
> can you explain why is **intellij-idea-community-edition** marked as nonfree? AFAIK, IDEA belongs to Apache 2.0 license.
I didn't add the community edition and am not aware why it was marked `nonfree`.
> why those other IDE's like CLion, WebStorm, etc. are marked as **restricted**, but not just **nonfree**? I've tried hard to find any info on JetBrains' website about them banning the redistribution of binary packages, but had no luck.
I believe Void prohibits distribution of binary-only software.
As a guess, since most commercial licensed software has some kind of restriction on redistribution, it is difficult to ensure that an agreement to redistribute is obtained and kept for legal purposes later on, so it is often easier to simply not redistribute.
next prev parent reply other threads:[~2020-09-29 4:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-9299@inbox.vuxu.org>
2020-01-19 18:37 ` voidlinux-github
2020-03-05 17:07 ` 2asoft
2020-09-27 22:53 ` Logarithmus
2020-09-28 1:32 ` 2asoft
2020-09-29 4:51 ` 2asoft [this message]
2020-10-12 13:56 ` virus-found
2020-10-12 13:56 ` virus-found
2020-10-14 14:59 ` 2asoft
2021-01-21 18:40 ` ericonr
2021-01-21 18:40 ` [ISSUE] [CLOSED] " ericonr
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=20200929045149.g5axYGYyEv3qu_GuPcWv_lstpNF9Y1sU3tMpqkQDdV8@z \
--to=2asoft@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).