Dear all,
I'd like to have your opinion about the policy for Tizen release names,
versions etc.
There's a definition of the release name and version in
platform/upstream/tizen-release, but this information is only stored
there and not accessible to other packages (except if one package
BuildRequires tizen-release and sources some files, which never happens
AFAIK).
Recently, I opened the bug TC-1599 [1] because there's a risk of
inconsistency in this information that could be defined in multiple places.
To solve this, I'd like to propose a solution where a few extra macros
are defined in the OBS project configuration, using the following scheme
that extends the existing one (example on Tizen:Common):
#####################################################################
%profile common
%release_name Tizen3/Common
%tizen_version_major 3
%tizen_version_minor 0
%tizen_version_patch 0
%tizen_version %{tizen_version_major}.%{tizen_version_minor}
%tizen_full_version %{tizen_version}.%{tizen_version_patch}
#####################################################################
You'll notice that I kept tizen_version as previously defined ('3.0'),
for compatibility reasons.
With these new global definitions, platform/upstream/tizen-release can
be cleaned up: all hardcoded values can be removed from the package.
If anyone knows other packages where hardcoded values for release name
and version are found, please report here (or on TC-1599)
Your feedback is appreciated.
Best regards,
Stéphane
[1] https://bugs.tizen.org/jira/browse/TC-1599
--
Stéphane Desneux
Intel OTC - Vannes/FR
gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
