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

[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 <ross.burton at intel.com> wrote:
> > 
> > On 26 June 2015 at 16:19, Khem Raj <raj.khem at gmail.com <mailto:raj.khem at gmail.com>> 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 fine tarballs released for QT5 too, just because its simpler to developer and integrate packages.
> > 
> > But oe-core is a system for integrating software...  If you're doing lots of work against weston, then a bbappend to change the SRC_URI to a git repository isn't exactly hard work.
> 
> yes and its done like that and what you are saying is that we limit OE to not help there. Its fine. We are now in a phase where we should be upstreaming the patches we are hosting in meta data for OE or elsewhere and git based workflow makes it easy for such work atleast for components which use git upstream. Preparing in same sandbox and test them out becomes simpler.
> 
> > 
> > Tarballs give us much smaller downloads, the security of checksums, and the general assurance that you're building what the maintainer expects you to build.
> 
> then we patch it on top of tarballs maintainer doesn’t want you to do that as well isnt it ?
> its lot easier to maintain using a SCM when we have patches and usually there are patches in OE. In any case, I will post a tarball version, and override the SRC_URI internally its not an issue its just another one thing to maintain on top of others. if thats what community wants, but I will need more folks to also express there usecase and opinion moving forward this is applicable to many components.

We did this in few cases earlier and I hate it, mostly because the
foo_1.2.3.bbappend changes SRC_URI and git and usually also sets PV to
something newer, so

foo_1.2.3.bb + foo_1.2.3.bbappend is building version 2.0+git which is
at least a bit confusing.

Other option of foo.bb in our layer with:
  require meta/recipes-bar/foo/foo_1.2.3.bb
  PV = "2.0+gitr${SRCPV}"
  ....
is also a bit annoying e.g. when upgrading oe-core and parsing failing
because foo_1.2.3.bb was upgraded to foo_1.2.4.bb by uprev script in
oe-core.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150629/d0e8e037/attachment-0002.sig>