Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] jimsh: new package
Date: Thu, 06 Sep 2012 08:37:31 -0300	[thread overview]
Message-ID: <50488AFB.9020205@zacarias.com.ar> (raw)
In-Reply-To: <50483D77.40902@mind.be>

On 09/06/12 03:06, Arnout Vandecappelle wrote:

>  I guess a patch that installs usb_modeswitch's tcl script will follow
> then?
> 
>  You'll probably want to add a hidden BR2_NEEDS_TCLSH which selects
> JIMSH if TCL is not defined.  And/or a HAS_TCLSH that is selected by
> jimsh and tcl.  Or should those symbols only be introduced when a
> package actually selects or depends on them?

I'm on the HAS_TCLSH side since there aren't many tclsh-using packages
at the moment, and there may be some (sick) valid reason for both with
jimsh not being as complete as full Tcl.
But that's for another patch when (if) jimsh gets in, it's not the first
iteration, there was one last year that went by silently :)
Regards.

      reply	other threads:[~2012-09-06 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 17:00 [Buildroot] [PATCH] jimsh: new package Gustavo Zacarias
2012-09-06  6:06 ` Arnout Vandecappelle
2012-09-06 11:37   ` Gustavo Zacarias [this message]

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=50488AFB.9020205@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