[Starlingx-discuss] [RFC] StarlingX Developer Guide

[Liu, ZhipengS]

Hi Abraham and all,

I have some proposals as below.

In current developer guide, we have 2 containers for mirror download and build.
Can we change it to only use 1 container for both? We will have 2 benefits at least
1) Simplify developer guide and remove some steps, such as mirror copy.
2) Developer can do mirror integrity check before start building.
     We always encounter this kind of issue that when build has been started for a while, then it told us some package missing. If we can do integrity check before building, it will be friendly to
Developer.

For mirror integrity check, just need to check if local mirror is complete compare to the latest 
Download list. If not, need download missing package first before start building.

Zhipeng







-----Original Message-----
From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] 
Sent: 2018年7月26日 10:13
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:	

- Repo status checked 7/25/2018 19:12 PST
- stx-tools master branch
  - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros
- Temporal! Changes, already in Developer Guide
   - RPM: selinux-policy-devel required
      https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
[1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss