From: Tissevert <tissevert+guix@marvid.fr>
To: 48126@debbugs.gnu.org
Subject: [bug#48126] [PATCH] Add package for vim-solarized
Date: Fri, 30 Apr 2021 22:44:18 +0200 [thread overview]
Message-ID: <20210430224418.01cc7669@pine.local> (raw)
In-Reply-To: <20210430194235.1461cada@pine.local>
Hello again,
I'm sorry I've just noticed that I set the wrong license in my package, I
hadn't checked it at the time when I first wrote it and forgot to edit it today
when I cleaned and sent it. Trouble is, I have no idea what the actual license is:
From Ethan Schoonover's original repository[1] it seems to be the MIT license but
- I can't find it in guix/license.scm, is that even an admissible free license ?
- The existing emacs-solarized-theme[2] package shipped with guix is distributed
under a gpl3 license ?! (how is that possible ? can one redistribute software
under a different license than its original one ? I assume it's because
solarized-emacs is builds on solarized but adds something more ?) Then, I see
that the main solarized repository imported an emacs theme[3] (a different one
it seems) and put it under the MIT license as well…
Can we distribute vim-solarized ? If yes, under what license ? If not, do I
have to build a separate independant vim color theme for solarized and version
it under a free license like bbatsov did ?
[1]: https://github.com/altercation/solarized
[2]: https://github.com/bbatsov/solarized-emacs
[3]: https://github.com/altercation/solarized/tree/master/emacs-colors-solarized
Tissevert
next prev parent reply other threads:[~2021-04-30 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 17:42 [bug#48126] [PATCH] Add package for vim-solarized Tissevert
2021-04-30 20:44 ` Tissevert [this message]
2021-04-30 22:06 ` Tobias Geerinckx-Rice via Guix-patches via
2021-04-30 23:20 ` Tobias Geerinckx-Rice via Guix-patches via
2021-04-30 23:27 ` Tobias Geerinckx-Rice via Guix-patches via
2021-05-04 20:56 ` Tissevert
2021-05-14 17:10 ` Tissevert
2021-05-14 18:25 ` Thiago Jung Bauermann via Guix-patches via
2021-05-14 20:33 ` Tissevert
2021-05-15 13:04 ` bug#48126: " Tobias Geerinckx-Rice via Guix-patches via
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=20210430224418.01cc7669@pine.local \
--to=tissevert+guix@marvid.fr \
--cc=48126@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.