From: Marko Lindqvist <cazfi74@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] RFC: Add recipe of gtk3 version of vte alongside gtk2 one.
Date: Sun, 26 May 2013 17:03:28 +0300 [thread overview]
Message-ID: <cover.1369576071.git.cazfi74@gmail.com> (raw)
RFC only! Patch is only build-tested.
Last gtk2-compatible version of vte is 0.28.2 currently present on OE core.
Later versions depend on gtk3. Since gtk3 exist in OE core, it would make
sense to be able to build version of vte (and other similar packages)
that does not depend on gtk2. Otherwise we end with systems that must
contain both gtk2 (to be used by some programs) and gtk3 (to be used by
other programs).
This patch just adds new recipe for latest vte version, 0.34.5, alongside
with 0.28.2 version.
How should priorities be set? "1" for gtk2-version, so it gets selected despite gtk3-version being newer?
- ML
The following changes since commit 8f5bc47729edb8cb051d81e9ff1680cb8d2eca25:
dropbear: a fix for hang in dropbearkey, built for x32 (2013-05-24 14:14:30 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib cazfi/rfc
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=cazfi/rfc
Marko Lindqvist (1):
vte: add 0.34.5 recipe
.../vte/vte-0.34.5/obsolete_automake_macros.patch | 14 ++++++++++++++
meta/recipes-support/vte/vte.inc | 4 +++-
meta/recipes-support/vte/vte_0.28.2.bb | 6 ++++--
meta/recipes-support/vte/vte_0.34.5.bb | 12 ++++++++++++
4 files changed, 33 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-support/vte/vte-0.34.5/obsolete_automake_macros.patch
create mode 100644 meta/recipes-support/vte/vte_0.34.5.bb
--
1.7.10.4
next reply other threads:[~2013-05-26 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 14:03 Marko Lindqvist [this message]
2013-05-26 14:03 ` [PATCH 1/1] vte: add 0.34.5 recipe Marko Lindqvist
2013-05-29 10:14 ` [PATCH 0/1] RFC: Add recipe of gtk3 version of vte alongside gtk2 one Burton, Ross
2013-05-29 22:14 ` Marko Lindqvist
2013-05-29 22:58 ` Otavio Salvador
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=cover.1369576071.git.cazfi74@gmail.com \
--to=cazfi74@gmail.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