On 7 August 2015 at 06:34, Khem Raj <raj.k...@gmail.com> wrote: > >> On Aug 6, 2015, at 1:42 AM, Jussi Kukkonen <jussi.kukko...@intel.com> wrote: >> >> Current releases of vte are LGPL 2.1+ but the one we have is still >> LGPL 2.0. >> >> Signed-off-by: Jussi Kukkonen <jussi.kukko...@intel.com> >> --- >> meta/recipes-support/vte/vte.inc | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/meta/recipes-support/vte/vte.inc >> b/meta/recipes-support/vte/vte.inc >> index 4081a7f..874062a 100644 >> --- a/meta/recipes-support/vte/vte.inc >> +++ b/meta/recipes-support/vte/vte.inc >> @@ -1,6 +1,6 @@ >> SUMMARY = "Virtual terminal emulator GTK+ widget library" >> BUGTRACKER = "https://bugzilla.gnome.org/buglist.cgi?product=vte"; >> -LICENSE = "LGPLv2.1+" >> +LICENSE = “LGPLv2.0" > > this brings to notice that this recipe needs upgrade > latest vte srcs already use LGPL2.1 may be updating to latest version is 0.40 > http://ftp.gnome.org/pub/gnome/sources/vte/0.40/
Yep, working on the upgrade lead me to finding this mistake... Anything above our current version of libvte will depend on GTK+3. That in itself is fine but I wanted to make sure I know the effects of that change before I send it: Not just if something will fail to compile (because it depends on GTK+2 and vte) but also if we end up compiling two versions of gtk+ in cases where we used to manage with one. Jussi >> DEPENDS = " glib-2.0 gtk+ intltool-native ncurses gobject-introspection-stub" >> RDEPENDS_libvte = "vte-termcap" >> >> -- >> 2.1.4 >> >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core > -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
