Bug 2882 - Include git hash in release tarball
Summary: Include git hash in release tarball
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.3
Assignee: Beth Flanagan
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-08-02 19:43 UTC by Darren Hart
Modified: 2012-08-27 21:24 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Hart 2012-08-02 19:43:23 UTC 
The release tarballs need to be self-identifying so they can be compared to the git source tree in case a problem is reported against the layer from someone using the tarball.
Comment 1 Beth Flanagan 2012-08-27 21:24:02 UTC 
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=0b030e70e0af27d87ba238d496b69edca49d9330

This is a two part fix. For all but the releases, we'll grab the git archive and name it with the hash name.

For releases, we will be including the release notes in the tarball which have the git hash.