From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Roadmap for LUA support in GRUB
Date: Wed, 11 Nov 2009 19:53:52 +0100 [thread overview]
Message-ID: <4AFB0840.5000802@gmail.com> (raw)
In-Reply-To: <e763acc10911111013s3ce034bfucf3afaecf87a6af1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Roman Shaposhnik wrote:
> Hi!
>
> On Wed, Nov 11, 2009 at 2:41 AM, Felix Zielcke <fzielcke@z-51.de> wrote:
>
>> Am Dienstag, den 10.11.2009, 19:38 -0800 schrieb Roman Shaposhnik:
>>
>>> Browsing the archives of grub-devel reveals that Lua support was moved to
>>> grub-extras which makes me ask these two questions:
>>> 1. Was the decision to move Lua based exclusively on the licensing concerns?
>>>
>> I don't think it was exclusively only decided because of the license,
>> but this is the top reason for it.
>>
>
> I'd appreciated knowing non-licensing reasons as well.
>
The only other reason was to encourage developpement of sh-like scripting.
> On the licensing front, though, what was an actual issue there?
> After all, Lua has a respectable FOSS license and I'm sure there's tons of
> MIT-licensed software in Debian. What made Lua different?
>
GNU isn't Debian. GNU has a very strong copyright policy and for code to
become GNU it usually has to be copyright-assigned to FSF. It's not the
case of LUA. So we created grub-extras specifically to hold code which
is perfectly legal, free and GPLv3-compatible but not suitable for GNU.
Any distribution which doesn't have anything against code not being
copyrighted by FSF shouldn't have any reason not to add grub-extras
--
Regards
Vladimir 'phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2009-11-11 18:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 3:38 Roadmap for LUA support in GRUB Roman Shaposhnik
2009-11-11 10:41 ` Felix Zielcke
2009-11-11 18:13 ` Roman Shaposhnik
2009-11-11 18:53 ` Vladimir 'phcoder' Serbinenko [this message]
2009-11-12 2:46 ` Roman Shaposhnik
2009-11-11 19:01 ` Felix Zielcke
2009-11-12 10:38 ` Robert Millan
2009-11-13 8:08 ` Roman Shaposhnik
2009-11-13 9:46 ` Felix Zielcke
2009-11-13 11:54 ` Vladimir 'phcoder' Serbinenko
2009-11-13 15:34 ` Roman Shaposhnik
2009-11-13 18:12 ` Bean
2009-11-13 18:29 ` Roman Shaposhnik
2009-11-13 19:06 ` Robert Millan
2009-11-13 19:34 ` Bean
2009-11-13 20:22 ` Vladimir 'phcoder' Serbinenko
2009-11-14 8:11 ` Bean
2009-11-14 12:29 ` Vladimir 'phcoder' Serbinenko
2009-11-13 20:54 ` Robert Millan
2009-12-29 4:24 ` Bruce O. Benson
[not found] ` <20100101114244.GE3692@thorin>
2010-01-02 7:35 ` Bruce O. Benson
2009-11-13 11:56 ` Robert Millan
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=4AFB0840.5000802@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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.
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.