From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Dexuan Cui <dexuan.cui@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] xterm: port the recipe from OE and upgrade to v278
Date: Thu, 05 Apr 2012 17:19:22 +0100 [thread overview]
Message-ID: <1567550.pQkNRWCquK@helios> (raw)
In-Reply-To: <db6ed82ab474a1b521b8f9bcb14abee243ac63a9.1333642153.git.dexuan.cui@intel.com>
On Friday 06 April 2012 00:10:12 Dexuan Cui wrote:
> The recipe is ported from OE:
> http://git.openembedded.org/openembedded/tree/recipes/xorg-app/xterm_266.bb
>
> I upgraded it from v266 to v278.
> I added LICENSE, LIC_FILES_CHKSUM and updated SRC_URI checksums.
I think it's unfortunate we have to pull in xterm just for the sake of showing
the qemu output - can we not use matchbox-terminal for this?
If we have to have it, Dexuan can you please compare this to the meta-oe xterm
recipe as that is likely to be more up-to-date than the one in OE-Classic?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-05 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 16:10 [PATCH 0/3] dexuan: build appliance: install xterm into the target [Apr 6, 2012] Dexuan Cui
2012-04-05 16:10 ` [PATCH 1/3] libxaw: move it from meta-demoapps/ into meta/ and upgrade it to 1.0.10 Dexuan Cui
2012-04-05 19:16 ` Martin Jansa
2012-04-06 3:50 ` Cui, Dexuan
2012-04-05 16:10 ` [PATCH 2/3] xterm: port the recipe from OE and upgrade to v278 Dexuan Cui
2012-04-05 16:19 ` Paul Eggleton [this message]
2012-04-05 16:47 ` Cui, Dexuan
2012-04-05 18:40 ` Martin Jansa
2012-04-05 16:10 ` [PATCH 3/3] task-self-hosted: install xterm into the target Dexuan Cui
2012-04-05 16:38 ` [PATCH 0/3] dexuan: build appliance: install xterm into the target [Apr 6, 2012] Saul Wold
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=1567550.pQkNRWCquK@helios \
--to=paul.eggleton@linux.intel.com \
--cc=dexuan.cui@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox