<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 26, 2015, at 9:59 AM, Burton, Ross <<a href="mailto:ross.burton@intel.com" class="">ross.burton@intel.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">On 26 June 2015 at 16:19, Khem Raj <span dir="ltr" class=""><<a href="mailto:raj.khem@gmail.com" target="_blank" class="">raj.khem@gmail.com</a>></span> wrote:<br class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">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.</div><div class=""></div></blockquote></div><br class="">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.</div></div></div></blockquote><div><br class=""></div><div>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. </div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""></div><div class="gmail_extra">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.</div></div></div></blockquote><div><br class=""></div><div>then we patch it on top of tarballs maintainer doesn’t want you to do that as well isnt it ?</div><div>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.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""></div><div class="gmail_extra">Ross</div></div>
</div></blockquote></div><br class=""></body></html>