Bug 2686

Summary:	linux-yocto/linux-yocto-custom: support low bandwidth options
Product:	[Yocto Project Subprojects] Kernel	Reporter:	Bruce Ashfield <bruce.ashfield>
Component:	linux-yocto	Assignee:	Bruce Ashfield <bruce.ashfield>
Status:	VERIFIED FIXED	QA Contact:
Severity:	enhancement
Priority:	Low	CC:	andreea.b.proca, jessica.zhang
Version:	1.4
Target Milestone:	1.4 M4
Hardware:	x86
OS:	Multiple
Whiteboard:	In design (revival of old code). 1.4 M2
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Bruce Ashfield 2012-07-03 19:44:54 UTC

To support low bandwidth configurations it is desirable to have options
for avoiding the full korg clone. This can be done via:

  a) shared/reference clones
  b) shallow clones
  c) git initialized repos based on a tgz

It should be noted that a) and b) can be fully functional linux-yocto repositories, 
while c) cannot.  As such, the tgz option can be an enhancement to linux-yocto-custom, 
but will not be a promoted method, since it goes against several best 
practices and kernel workflow options .. it also has a not insignificant
carrying cost.

Option c) only supports minimal configuration fragments and no git based 
merge options or feature descriptions. 

Options a) and b) are not currently planned for 1.3, but are listed here to be
complete and as options for 1.3+ (in particular option a)).

Comment 1 Bruce Ashfield 2012-09-24 14:41:20 UTC

Update: in case it isn't clear, this one is going to wait until 1.4, since we
don't want (yet again) something completely different for the kernel. 

It makes sense to wait for the fetcher changes with shallow clones, or 
other similar options before adding this support, since it is essentially
free after that.

tgz support can be considered and stacked AFTER the initial low bandwidth
options are working, since most of the issues with the revision chain not
being complete will already be tested and solved.

Comment 2 Bruce Ashfield 2013-01-24 04:35:26 UTC

tgz support is possible with linux-yocto-custom, shallow clones are still not
available, so we'll go with plan B for now. This still isn't ideal, but it does
fit the linux-yocto-custom model, so we can live with it.

Comment 3 Bruce Ashfield 2013-02-05 16:04:27 UTC

kernel-yocto/linux-yocto-custom: support low bandwidth options

To support configurations where active development is not being done within
the oe/bitbake build environment and restricted bandwidth situations, this
commit allows the SRC_URI to point to a kernel tgz instead of a full git
repository.

Outside of the upstream tgz instead of a kernel git repository, the
restrictions, config and patch process is the same as any linux-yocto-custom
recipe.

An example linux-yocto-custom based recipe would have a configuration like
this to build the 3.7 kernel, using an externally supplied config, from the
3.7 tgz:

  SRC_URI = "http://kernel.org/pub/linux/kernel/v3.0/linux-3.7.tar.bz2"
  PV = "3.7"
  S = "${WORKDIR}/linux-3.7"
  SRC_URI[md5sum] = "5323f3faadd051e83af605a63be5ea2e"
  SRC_URI[sha256sum] = "dc08d87a579fe2918362e6666e503a95a76296419195cb499aa9dd4dbe171a9e"

[YOCTO #2686]

(From OE-Core rev: 08b3a282ce75a9972694f0c4379179505b9ec91f)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Comment 4 Andreea Brandusa Proca 2013-04-11 11:17:59 UTC

Verified.