All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
	<openembedded-core@lists.openembedded.org>,
	"Burton, Ross" <ross.burton@intel.com>,
	Khem Raj <raj.khem@gmail.com>
Subject: Re: [PATCH 0/2] python: add tk support
Date: Mon, 5 Nov 2018 17:29:03 +0800	[thread overview]
Message-ID: <5BE00D5F.2050209@windriver.com> (raw)
In-Reply-To: <a17b1fae-4e22-35eb-3602-3a3725fd60e4@windriver.com>



On 2018年10月30日 12:52, Randy MacLeod wrote:
> On 10/29/18 8:51 AM, Burton, Ross wrote:
>> Terrified to ask, but why?
>> On Thu, 25 Oct 2018 at 09:39, <mingli.yu@windriver.com> wrote:
>>>
>>> 1, move tk recipe from meta-oe
>>> 2, enable tk to add tk support
>
> Well, tcl and tk do go together and Khem's comment from 2013
> suggested that it might be pulled into oe-core some day.
>
> I think what started us down this path is a FACE [1] compliance test.
> If there's resistance to moving the package to oe-core, can we
> enable python-tk even if tk stayed in meta-oe, Grace?
> Also, this should be done using using PACKAGECONFIG?
> Finally, what about python3-tk ?

Will send out v2 to use PACKAGECONFIG for tk and add tk support for 
python3 altogether.

Thanks,

>
> ../Randy
>
> [1] https://en.wikipedia.org/wiki/Future_Airborne_Capability_Environment
>>> --
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


      parent reply	other threads:[~2018-11-05  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  8:39 [PATCH 0/2] python: add tk support mingli.yu
2018-10-25  8:39 ` [PATCH 1/2] tk: add new recipe(move from meta-oe) mingli.yu
2018-10-25  8:39 ` [PATCH 2/2] python: add tk support mingli.yu
2018-10-25  9:08 ` ✗ patchtest: failure for " Patchwork
2018-10-29 12:51 ` [PATCH 0/2] " Burton, Ross
2018-10-30  4:52   ` Randy MacLeod
2018-10-30 11:11     ` Burton, Ross
2018-11-05  9:29     ` Yu, Mingli [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=5BE00D5F.2050209@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=randy.macleod@windriver.com \
    --cc=ross.burton@intel.com \
    /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.