Hello,
In the proposed wiki page for Tizen Distro Workflow
https://wiki.tizen.org/wiki/Tizen-Distro_Workflow
I would like to open the discussion on the specific issue of maintaining
Tizen evolution and resynchronisation with newer release of Yocto.
1) Source code sync seems covered
-----------------------------------------------
My reading is that for the majority of our work which is modifying code,
the process covers the need.
The code would be changed in git which is reviewed in gerrit and
triggers a test build in a Yocto buildbot and then a build in an OBS.
Code is unique but shared by the two build systems.
"only tricky" cases will be induced by code which will build on one
subsystem and not on the other.
So far, I am happy to assume that is will be rare.
2) A change is required in the Meta-data
----------------------------------------------------
For any reason a change is required in the building meta data, new
dependency, special case to support and architecture, ...
In reality those changes are not frequent but do occurs.
I would like to better understand your proposition. Could you please
confirm or reject my understanding and explain better what is your
proposition if you feel that I missed the point.
A) The developer should do a modification on the Yocto side (bb files/
layers) as the OBS side (spec) are generated automatically from the bb
files/layers.
B) Should the developer always create a bbappend file to contain his
changes or can he patch the bb files directly.
Note the later is far easier for him but make the realignment with the
next revision of Yocto would be become more complex.
Could you explain your vision on the process when a realignment with
Yocto will be required.
C) In your proposal, the bb files would be associate to each package in
Tizen what is different from the traditional Yocto unified model.
How the developer will have a view of all the meta data affecting his
package in order to propose a change from that reduced vision ?
D) How do you propose to handle changes which would spread over multiple
packages which are managed in the project conf on OBS.
Where will that code reside ? How will maintain it ? What about future
realignment with new Yocto release ?
E) The layers are by nature covering the building of multiple packages
for most of them. Where will they be maintained for Tizen ? Who will be
the maintainers ?
F) In the rare case where the package will build under Yocto but will
fail on OBS, what will be the tool for the developer to help him to fix
the issue knowing that the spec file is generated from the bb files ?
Thanks in advance for your clarifications.
--
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
