Bug 6130 - Document manifest creation python class/routine
Summary: Document manifest creation python class/routine
Status: VERIFIED NOTABUG
Alias: None
Product: General Docs
Classification: Documentation
Component: docs-general (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 1.7 M3
Assignee: Scott Rifenbark
QA Contact: Stoicescu Cornel
URL:
Whiteboard: 13 June 2014: RESOLVED
Depends on:
Blocks:
 
Reported: 2014-04-08 14:41 UTC by Scott Rifenbark
Modified: 2014-07-16 11:26 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 Scott Rifenbark 2014-04-08 14:41:41 UTC
We need to complete the documentation part for the https://bugzilla.yoctoproject.org/show_bug.cgi?id=5704 bug, which had the documentation flag set to "Yes."

Here are some comments from that bug to help start:

Laurentiu Palcu: 
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.

Laurentiu Palcu:
Patches merged: 54 patches, starting commit:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=095bb006c3dbbfbdfa05f13d8d7b50e2a5ab2af0

Scott Rifenbark:
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 1 Paul Eggleton 2014-04-10 14:51:36 UTC
Laurentiu - could you please give Scott some assistance for background on this? Thanks.
Comment 2 Scott Rifenbark 2014-04-22 18:57:50 UTC
Setting to NEEDINFO.
Comment 3 Laurentiu Palcu 2014-05-29 06:38:59 UTC
We don't really need new documentation for this. Indeed, the final manifest is unchanged. The initial manifest is used in the rootfs creation process but the end user doesn't actually directly use this one. It's internal.
Comment 4 Scott Rifenbark 2014-06-13 06:02:17 UTC
Hi, 

Per Comment 3 from Laurentiu, I am setting this bug to RESOLVED/NOTABUG and turning the documentation flag to "No".

Scott
Comment 5 Scott Rifenbark 2014-06-19 04:50:56 UTC
Set to M3 to get this off the lists.  It is RESOLVED.

Scott
Comment 6 Stoicescu Cornel 2014-07-16 11:26:56 UTC
Verified.