Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-29 Thread Martin Jansa
On Fri, Jun 26, 2015 at 10:37:57AM -0700, Khem Raj wrote: > > > On Jun 26, 2015, at 9:59 AM, Burton, Ross wrote: > > > > On 26 June 2015 at 16:19, Khem Raj > > wrote: > > From a system integrators point of view, I agree with your sentiments. From > > a developers poi

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-29 Thread Martin Jansa
On Fri, Jun 26, 2015 at 08:19:58AM -0700, Khem Raj wrote: > > > On Jun 26, 2015, at 7:47 AM, Burton, Ross wrote: > > > > > > On 3 June 2015 at 22:21, Khem Raj > > wrote: > > > Can you explain why? The revision looks like 0.16.0 release. > > > > its easy to develop l

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-26 Thread Khem Raj
> On Jun 26, 2015, at 9:59 AM, Burton, Ross wrote: > > On 26 June 2015 at 16:19, Khem Raj > wrote: > From a system integrators point of view, I agree with your sentiments. From a > developers point of view not so much. We already have many recipes already > fetching

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-26 Thread Burton, Ross
On 26 June 2015 at 16:19, Khem Raj wrote: > From a system integrators point of view, I agree with your sentiments. > From a developers point of view not so much. We already have many recipes > already fetching from git and more and more switching to use it see qt5 > lately, there are perfectly fi

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-26 Thread Khem Raj
> On Jun 26, 2015, at 7:47 AM, Burton, Ross wrote: > > > On 3 June 2015 at 22:21, Khem Raj > wrote: > > Can you explain why? The revision looks like 0.16.0 release. > > its easy to develop libinput and prepare/test upstream patches since all > upstreams want the pa

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-26 Thread Burton, Ross
On 3 June 2015 at 22:21, Khem Raj wrote: > > Can you explain why? The revision looks like 0.16.0 release. > > its easy to develop libinput and prepare/test upstream patches since all > upstreams want the patches against their latest master and its easy to > switch to AUTOREV locally and do it.

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Khem Raj
> On Jun 3, 2015, at 1:18 PM, Jussi Kukkonen wrote: > >> Use git for repo for SRC_URI > > Can you explain why? The revision looks like 0.16.0 release. its easy to develop libinput and prepare/test upstream patches since all upstreams want the patches against their latest master and its easy t

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Jussi Kukkonen
On 3 June 2015 at 19:41, Khem Raj wrote: > Use git for repo for SRC_URI Can you explain why? The revision looks like 0.16.0 release. > copyright year changed for weston compositor.c > > - * Copyright © 2012 Collabora, Ltd. > + * Copyright © 2012-2014 Collabora, Ltd. > > libinput license changes

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Khem Raj
> On Jun 3, 2015, at 11:56 AM, Burton, Ross wrote: > > > On 3 June 2015 at 19:07, Khem Raj > wrote: > They are interdependent thats why they are together. Splitting wont > get us anything moreover it will break git bisect > > Upgrading the Wayland protocol is indepe

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Khem Raj
> On Jun 3, 2015, at 11:56 AM, Burton, Ross wrote: > > Upgrading the Wayland protocol is independent from upgrading Weston. > libinput can be upgraded independently of Weston. They have an implied > ordering (wayland before weston, libinput before weston) but they're not > single unit. >

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Burton, Ross
On 3 June 2015 at 19:07, Khem Raj wrote: > They are interdependent thats why they are together. Splitting wont > get us anything moreover it will break git bisect > Upgrading the Wayland protocol is independent from upgrading Weston. libinput can be upgraded independently of Weston. They have

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Khem Raj
On Wed, Jun 3, 2015 at 10:09 AM, Burton, Ross wrote: > > On 3 June 2015 at 17:41, Khem Raj wrote: >> >> Use git for repo for SRC_URI >> >> copyright year changed for weston compositor.c >> >> - * Copyright © 2012 Collabora, Ltd. >> + * Copyright © 2012-2014 Collabora, Ltd. >> >> libinput license

Re: [OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Burton, Ross
On 3 June 2015 at 17:41, Khem Raj wrote: > Use git for repo for SRC_URI > > copyright year changed for weston compositor.c > > - * Copyright © 2012 Collabora, Ltd. > + * Copyright © 2012-2014 Collabora, Ltd. > > libinput license changes are > - COPYING: note that having linux/input.h in the tree

[OE-core] [PATCH 1/4] wayland/weston/libinput: Upgrade to 1.6.0 -> 1.8.0

2015-06-03 Thread Khem Raj
Use git for repo for SRC_URI copyright year changed for weston compositor.c - * Copyright © 2012 Collabora, Ltd. + * Copyright © 2012-2014 Collabora, Ltd. libinput license changes are - COPYING: note that having linux/input.h in the tree does not make libinput GPL - Updated to 2015 where appropr