RFC: Add recipe of gtk3 version of vte alongside gtk2 one.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | vte: add 0.34.5 recipemeta/ meta/ meta/ +1 more | +33 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] RFC: Add recipe of gtk3 version of vte alongside gtk2 one.
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
Signature · 1 line
1.7.10.4