Use new eltf_params_updates.xml for later ELTF autoupdate

LXCR-7377 Change to allow ELTF to autoupdate all parameters
in the release info and the open-source books.

All parameters, including also multiline commands
and complete tables of all target machine parameters
are stored in one file eltf_params_updates.xml
Prepared for auto-updating by ELTF by using a template
elft_params_template.xml with ELTF_* variables
from which a new eltf_params_updates.xml can be created
and pushed (if changed)

This includes the -b option to the repo command, which is
the branch or tag of the MANIFEST. This is what the user
uses to get the source. In a final distribution this tag
shall be same as the tag given in manifest_conf.mk

Left is manifest_conf.mk but MANIFESTHASH can
be overridden by an env.variable when building.
MANIFESTHASH still defines which MANIFEST to clone
when building the doc to get a list of valid MACHINE names
and to get the valid build/boot commands from the MANIFEST.

Left is also pardoc-distro.xml with three version variables
used by gen_known_issues.py and gen_pkgdiff.py

Signed-off-by: Lennart Johansson <lennart.johansson@enea.com>

1 files changed, 20 insertions, 10 deletions

diff --git a/doc/book-enea-linux-release-info/doc/main_changes.xml b/doc/book-enea-linux-release-info/doc/main_changes.xml
index 223aa42..38fec86 100644
--- a/doc/book-enea-linux-release-info/doc/main_changes.xml
+++ b/doc/book-enea-linux-release-info/doc/main_changes.xml
@@ -5,21 +5,29 @@
   <title>Main Changes</title>
 
   <para>This chapter describes the major changes and additions in the Enea
-  Linux release compared to the previous release (Enea Linux 5.0-ppc).</para>
+  Linux release compared to the previous release (Enea Linux
+  5.0-ppc).<remark>INFO Just now Hardcoded previous release string in this
+  paragraph.</remark><remark>The list of changed packages further down is
+  created from the open source book licenses.xml by the script gen_pkgdiff.py
+  by comparing with an older open source licenses.xml, depending on the
+  parameter "prev_baseline" in pardoc-distro.xml, e.g. a tag like "EL5". This
+  parameter needs to be changed to a new TAG when a release info for another
+  EL version is created. It must correspond to the release string
+  above.</remark></para>
 
   <section id="relinfo-changes-other">
     <title>New Functionality/Enhancements</title>
 
-    <remark>Based in the Jira query: 'project = CPDX and fixVersion = "Enea
-    Linux 6"'</remark>
-
     <itemizedlist spacing="compact">
       <listitem>
-        <para>New Yocto version (<xi:include
-        href="../../s_docsrc_common/pardoc-distro.xml"
+        <para>New Yocto version (<xi:include href="eltf_params_updated.xml"
+        xmlns:xi="http://www.w3.org/2001/XInclude"
+        xpointer="element(Yocto_VER/1)" />). See <xi:include
+        href="eltf_params_updated.xml"
         xmlns:xi="http://www.w3.org/2001/XInclude"
-        xpointer="element(Yocto_VER/1)" />). See <ulink
-        url="https://www.yoctoproject.org/downloads/core/krogoth21">https://www.yoctoproject.org/downloads/core/krogoth21</ulink>.</para>
+        xpointer="element(ULINK_YOCTO_PROJECT_DOWNLOAD/1)" />).<remark>INFO
+        Yocto_VER and ULINK_YOCTO_PROJECT_DOWNLOAD in
+        eltf_params_updated.xml</remark></para>
       </listitem>
 
       <listitem>
@@ -36,13 +44,15 @@
   <section condition="hidden" id="relinfo-fixed">
     <title>Problems Fixed in this Release</title>
 
-    <para>TBD <remark>FIXME or set condition hidden</remark></para>
+    <para>TBD <remark>FIXME or set condition hidden on the section
+    element</remark></para>
   </section>
 
   <section condition="hidden" id="relinfo-added-drivers">
     <title>Added Drivers</title>
 
-    <para>TBD <remark>FIXME or set condition hidden</remark></para>
+    <para>TBD <remark>FIXME or set condition hidden on the section
+    element</remark></para>
   </section>
 
   <xi:include href="pkgdiff_generated.xml"