Bug 5704 - Write manifest creation python class/routine
Summary: Write manifest creation python class/routine
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 1.6
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard: 08 April 2014: Setting documentation ...
Depends on:
Blocks: 4779 4780 4781
  Show dependency tree
 
Reported: 2014-01-06 09:58 UTC by Laurentiu Palcu
Modified: 2014-04-08 15:02 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laurentiu Palcu 2014-01-06 09:58:55 UTC
This is part of the rootfs refactoring work. The new class/routine should be responsible of creating two type of manifests: an initial one, used by the rootfs creation routines to generate the rootfs and a final one, which will contain all the packages installed in the image.
Comment 1 Laurentiu Palcu 2014-02-14 14:47:29 UTC
Patches merged: 54 patches, starting commit:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=095bb006c3dbbfbdfa05f13d8d7b50e2a5ab2af0
Comment 2 Scott Rifenbark 2014-04-02 14:20:06 UTC
Hi, 

In the ref-manual where we talk about image generation (http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#image-generation-dev-environment) we mention some information about creation of manifest file.  From looking at this bug fix, the changes that cause two types of manifests to be created don't really surface to the user.  We still have the one final manifest file correct? 

Also, we have a description of the IMAGE_MANIFEST variable at http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#var-IMAGE_MANIFEST.  Is this affected?

I am thinking we don't need additional user documentation changes for this fix but I could be wrong.  Please examine these two sections and advise on any changes that the user needs to know about.

Thanks, 
Scott
Comment 3 Scott Rifenbark 2014-04-08 15:02:04 UTC
Hi, 

We can't get the doc change done in time for the 1.6 release.  I have opened a new bug to track fixing the documentation for this issue.  See Bug 6130.

Scott