Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] ruby2 buildroot packaging
Date: Thu, 25 Apr 2013 12:52:54 -0300	[thread overview]
Message-ID: <51795156.3050309@zacarias.com.ar> (raw)
In-Reply-To: <CA+pfegGAmGc24BoFVh5SJ4VO8tZCE5DitQobfjj=EGF4UFj6vA@mail.gmail.com>

On 04/25/2013 10:45 AM, Murat Demirten wrote:

> Hi Gustavo,
> 
> Do you have any plans or any free time to package ruby2 for buildroot?
> 
> If not and if I can find a time for this, I want to prepare package for
> ruby2 
> 
> I think there must be two independent package like ruby and ruby2 for
> version 1.9.X and version 2.
> 
> Do you agree that? What is your opinions?
> 
> Regards,

Hi.
I'm copying the list since someone else might be interested as well.
At the moment i have no time to package ruby2, and yes, doing a separate
package is probably wise given the differences.
So feel free to work on it unless someone else has already done so and
didn't send a patch yet.
Regards.

           reply	other threads:[~2013-04-25 15:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CA+pfegGAmGc24BoFVh5SJ4VO8tZCE5DitQobfjj=EGF4UFj6vA@mail.gmail.com>]

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=51795156.3050309@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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