Re: [PATCH/RFC 0/7] Support for Ruby
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Sep 28, 2013, 22:57 UTC
- Message-ID
- <CAMP44s2Fg2NwinKTDrHjKhKQkniwAZD041n8QYrN5oOjOJ8osQ@mail.gmail.com>
- In-Reply-To
- <20130923014157.GE235845@vauxhall.crustytoothpaste.net>
On Sun, Sep 22, 2013 at 8:41 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:
Show 16 quoted lines
> On Sun, Sep 22, 2013 at 05:00:44PM -0700, Junio C Hamano wrote: >> - Moving away from higher-level scripting languages such as shell and Perl. >> Recent "clean --interactive" may have added some code that could be >> reused for a rewrite of "add -i" (which I think is in Perl), for example. >> The minimum "You need to have these to use Git" should be made more >> portable by doing *less* in shell or Perl, not by adding more in the higher- >> level languages, and certainly not by adding other languages, be it Ruby or >> Lua. > > I can certainly go for that. C is faster and the codebase can be more > consistent (and more portable to non-Unix). My concern was that if > we're going to be adding additional languages, some previous warning > would be appropriate. As I said, I wouldn't be able to deploy a git > using Ruby immediately, and I'm sure I'm not the only one. If we're not > going to be adding another language, then obviously the issue becomes > moot.
You could just build with NO_RUBY=y. Problem solved.
-- Felipe Contreras