From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: onivim2-0.5.5
Date: Mon, 24 May 2021 17:49:40 +0200 [thread overview]
Message-ID: <20210524154940.dQjcZRk_zYTJtnZYWQ2wLdsJLYf-1FVdz_m9-3pozWw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31076@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
New comment by FollieHiyuki on void-packages repository
https://github.com/void-linux/void-packages/pull/31076#issuecomment-847140379
Comment:
@kawaiiamber what I meant was to use `yarn` instead of `npm`.
Packaging the MIT code is a bad idea. It will have no security fixes, etc. It is just the 1.5 years behind snapshot of the main code base with the license changed. So ... the licensing model is worse then Vscode :(
> Since onivim2 doesn't allow distribution, does this mean the AUR is in license violation as it pulls from the current repo, not the mit one? https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=onivim2
The AUR and our `restricted` packages doesn't provide binaries or the source code. They only have the build instructions, and the users are the ones pulling the source themselves. So it is not a violation.
next prev parent reply other threads:[~2021-05-24 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 8:32 [PR PATCH] " kawaiiamber
2021-05-23 11:55 ` FollieHiyuki
2021-05-23 16:17 ` F0Xde
2021-05-23 16:33 ` ericonr
2021-05-23 17:04 ` FollieHiyuki
2021-05-23 23:51 ` kawaiiamber
2021-05-23 23:54 ` kawaiiamber
2021-05-23 23:55 ` kawaiiamber
2021-05-24 0:00 ` kawaiiamber
2021-05-24 11:38 ` kawaiiamber
2021-05-24 11:45 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-24 11:46 ` kawaiiamber
2021-05-24 11:58 ` kawaiiamber
2021-05-24 15:49 ` FollieHiyuki [this message]
2021-05-25 0:32 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-25 0:33 ` kawaiiamber
2021-05-25 0:35 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-25 0:41 ` kawaiiamber
2022-05-20 2:12 ` github-actions
2022-06-18 2:12 ` [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=20210524154940.dQjcZRk_zYTJtnZYWQ2wLdsJLYf-1FVdz_m9-3pozWw@z \
--to=folliehiyuki@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).