All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 13 Nov 2009 12:54:02 +0100	[thread overview]
Message-ID: <4AFD48DA.2050903@gmail.com> (raw)
In-Reply-To: <e763acc10911130008u42bf8c08wb39a5967af34e4ee@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]

Roman Shaposhnik wrote:
> On Thu, Nov 12, 2009 at 2:38 AM, Robert Millan <rmh@aybabtu.com> wrote:
>   
>> First of all, there's no license problem.  We usually write our own code, but
>> when we have specific reasons to import it from another project, any license
>> that is compatible with GPL (v3 and later) would be considered suitable.
>>     
>
> Aha! So the Lua license really is a red herring here..
>
>   
We already explained the reasons. Grub-extras is for code which is for
imported code ehich doesn't need to reside in main trunk to be
functional. ZFS is a similar case. On the other hand LZMA needs to be in
main trunk. Occasionally exceptions may occur but it doesn't discard
general rule.
>> However, we only import code from external projects when there's an important
>> reason to do so.  For example, we imported LZMA code because we needed the
>> best compression around, and we didn't want to reinvent the wheel.  In the
>> specific case of LUA, this compromise didn't make sense to us since we already
>> had a scripting engine.
>>     
>
> ...the real reason seems to be that you don't really believe in Lua as a primary
> scripting language for GRUB, correct?
>
>   
Please don't become personal on this. Except rescue parsers all parsers
are implemented the same way and can replace one another. So what do you
mean by "primary scripting language"? If what you mean is just one being
default then no project can make default which suit all usres. It's what
configuration is for. If you speak about invested efforts then you can't
force people to spend time on something they don't want (but you can pay
one of us to do stuff you need).
> IOW, the inclusion of Lua was more of a fluke than a deliberate
> decision of investing
> in a different scripting engine.
>
> This is not a value judgment -- just an attempt to figure things out.
> Personally I'm really
> excited about Lua. I see that a lot folks share my opinion (I can't
> wait to see Lua as
> a scripting engine for NetBSD kernel, for example) and I thought that
> GRUB project
> was among these folks.
>   
As I said you can't ask everyone to share your language preferences. But
patches are of course welcome
> Thanks,
> Roman.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  parent reply	other threads:[~2009-11-13 11: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
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 [this message]
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=4AFD48DA.2050903@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.