On 11/28/2014 02:33 PM, Dominig ar Foll (Intel OTC) wrote:
Le 28/11/2014 09:10, Markus Lehtonen a écrit :
There would be a distinction between "fully automatically maintained"
spec
files and "semi-automatically" maintained spec files.
For the fully automatic case, spec metadata would be auto-generated and
pushed to git on every ref update, effectively overwriting any manual
changes. In the semi-automatic case there would be no automatic push to
the branch but a patch would be submitted to gerrit, instead. This would
allow some maintainer control (with a risk of some meta data divergence,
unfortunately) and not force to use bb metadata outright.
The distinction between the fully/semi automatic would be defined in the
bb metadata of the package.
Thus, changes to .spec file are not explicitly denied (I don't even know
how to implement something like that) but changes might get
automatically
overwritten (for the fully automatic packages).
Ed,
having such exception will not be manageable and shall not be enabled.
If for any reason the business logic of the bb->spec translator is
known to fail on a given list of packages due to their very weird
construction, the tool will need to embedded a special logic for those
packages.
This is not very different of the model used in the tool spec2yocto
which has been used to prototype Tizen build on Yocto earlier this year.
Having a dual maintenance model is not an acceptable solution.
More information regarding the spec2yocto spec -> bb converter:
It is an internal tool whose goal is to automatically generate Yocto
recipes from Tizen RPM spec files instead of writing them manually. This
allows us to easily maintain the recipes aligned with the spec files
(and package versions) which would be to much work to be done manually.
We will keep using it as long as the OBS is the main build solution.
When Yocto will become the main build solution (and OBS the alternative)
we will stop using it and begin to maintain the recipes manually. At
this point the process will be reversed: spec files will be generated
from recipes. It is important to understand that the spec2yocto script
is a temporary tool made to facilitate the transition between an OBS and
a Yocto build.
This tool can be useful to people wanting to add new recipes to
meta-tizen and can be found in the repo: scm/bb/tizen:
git clone git://review.tizen.org/scm/bb/tizen
Basic usage of the spec2yocto tool is described in the file README.md.
If you find that some information are missing or encounter any errors,
we will be glad to help.
Best regards,
Kevin
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
