clarity of Layered Build Reference in StarlingX
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Won't Fix
|
Low
|
Scott Little |
Bug Description
The layered build doc is inaccurate in this way:
https:/
The descriptions of layers requirements is unclear for all members leading to build failures when attempts to add packages are not correctly presented in the layers. Interpersonal dialogues are not currently sufficient for transmitting the information as no-one really knows how it works. As this is a developer reference, it is also unclear what needs to be tested in what ways to make sure builds will not fail.
Specifically noted in this request:
- An RPM that must be on the ISO must be in the flock layer. The point "It is required to build the iso" should read "Add to the flock layer if it is required to build the iso". This sense is also is not otherwise within the current description of flock layer.
- A testing requirement section should added describing what developers must do before submitting code reviews
- What is the relationship between building a lower layer and subsequently building an ISO to test Starlingx? If one builds the compiler layer, can one then run 'build-iso' to get an install media.
tags: | added: stx.build |
description: | updated |
Changed in starlingx: | |
importance: | Medium → Low |
@Michel, thanks for submitting this doc bug against the Layered Build Reference.
There is another STX doc that provides step-by-step details, called the Layered Build Guide. /docs.starlingx .io/developer_ resources/ layered_ build_guide. html
https:/
Can you please review the other guide also? It is possible that your feedback should be addressed in both docs.
Thanks in advance,
Mary Camp