Hello community,
here is the log from the commit of package yast2-installation for openSUSE:Factory
checked in at Fri Dec 19 15:21:01 CET 2008.
--------
--- yast2-installation/yast2-installation.changes 2008-12-17 14:43:39.000000000 +0100
+++ /mounts/work_src_done/STABLE/yast2-installation/yast2-installation.changes 2008-12-18 18:05:31.000000000 +0100
@@ -1,0 +2,6 @@
+Thu Dec 18 18:04:47 CET 2008 - locilka@suse.cz
+
+- Updated control file documentation (bnc #438678).
+- 2.17.49
+
+-------------------------------------------------------------------
calling whatdependson for head-i586
Old:
----
yast2-installation-2.17.48.tar.bz2
New:
----
yast2-installation-2.17.49.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-installation.spec ++++++
--- /var/tmp/diff_new_pack.w18848/_old 2008-12-19 15:20:43.000000000 +0100
+++ /var/tmp/diff_new_pack.w18848/_new 2008-12-19 15:20:43.000000000 +0100
@@ -1,5 +1,5 @@
#
-# spec file for package yast2-installation (Version 2.17.48)
+# spec file for package yast2-installation (Version 2.17.49)
#
# Copyright (c) 2008 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
@@ -19,12 +19,12 @@
Name: yast2-installation
-Version: 2.17.48
+Version: 2.17.49
Release: 1
License: GPL v2 or later
Group: System/YaST
BuildRoot: %{_tmppath}/%{name}-%{version}-build
-Source0: yast2-installation-2.17.48.tar.bz2
+Source0: yast2-installation-2.17.49.tar.bz2
Prefix: /usr
BuildRequires: docbook-xsl-stylesheets doxygen libxslt perl-XML-Writer sgml-skel update-desktop-files yast2-core-devel yast2-devtools yast2-testsuite
# xmllint
@@ -126,7 +126,7 @@
Lukas Ocilka
%prep
-%setup -n yast2-installation-2.17.48
+%setup -n yast2-installation-2.17.49
%build
%{prefix}/bin/y2tool y2autoconf
@@ -197,6 +197,9 @@
%exclude %{prefix}/share/doc/packages/yast2-installation/COPYING
%exclude %{prefix}/share/doc/packages/yast2-installation/README
%changelog
+* Thu Dec 18 2008 locilka@suse.cz
+- Updated control file documentation (bnc #438678).
+- 2.17.49
* Wed Dec 17 2008 locilka@suse.cz
- Added yet another xset call (bnc #455771 comment #40)
- 2.17.48
++++++ yast2-installation-2.17.48.tar.bz2 -> yast2-installation-2.17.49.tar.bz2 ++++++
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/configure new/yast2-installation-2.17.49/configure
--- old/yast2-installation-2.17.48/configure 2008-12-16 12:11:39.000000000 +0100
+++ new/yast2-installation-2.17.49/configure 2008-12-18 18:07:04.000000000 +0100
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.63 for yast2-installation 2.17.47.
+# Generated by GNU Autoconf 2.63 for yast2-installation 2.17.48.
#
# Report bugs to http://bugs.opensuse.org/.
#
@@ -596,8 +596,8 @@
# Identity of this package.
PACKAGE_NAME='yast2-installation'
PACKAGE_TARNAME='yast2-installation'
-PACKAGE_VERSION='2.17.47'
-PACKAGE_STRING='yast2-installation 2.17.47'
+PACKAGE_VERSION='2.17.48'
+PACKAGE_STRING='yast2-installation 2.17.48'
PACKAGE_BUGREPORT='http://bugs.opensuse.org/'
ac_unique_file="RPMNAME"
@@ -1285,7 +1285,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures yast2-installation 2.17.47 to adapt to many kinds of systems.
+\`configure' configures yast2-installation 2.17.48 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1357,7 +1357,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of yast2-installation 2.17.47:";;
+ short | recursive ) echo "Configuration of yast2-installation 2.17.48:";;
esac
cat <<\_ACEOF
@@ -1437,7 +1437,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-yast2-installation configure 2.17.47
+yast2-installation configure 2.17.48
generated by GNU Autoconf 2.63
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
@@ -1451,7 +1451,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by yast2-installation $as_me 2.17.47, which was
+It was created by yast2-installation $as_me 2.17.48, which was
generated by GNU Autoconf 2.63. Invocation command line was
$ $0 $@
@@ -2298,7 +2298,7 @@
# Define the identity of the package.
PACKAGE='yast2-installation'
- VERSION='2.17.47'
+ VERSION='2.17.48'
cat >>confdefs.h <<_ACEOF
@@ -2522,7 +2522,7 @@
-VERSION="2.17.47"
+VERSION="2.17.48"
RPMNAME="yast2-installation"
MAINTAINER="Lukas Ocilka "
@@ -3711,7 +3711,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by yast2-installation $as_me 2.17.47, which was
+This file was extended by yast2-installation $as_me 2.17.48, which was
generated by GNU Autoconf 2.63. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -3761,7 +3761,7 @@
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_version="\\
-yast2-installation config.status 2.17.47
+yast2-installation config.status 2.17.48
configured by $0, generated by GNU Autoconf 2.63,
with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\"
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/configure.in new/yast2-installation-2.17.49/configure.in
--- old/yast2-installation-2.17.48/configure.in 2008-12-16 12:11:36.000000000 +0100
+++ new/yast2-installation-2.17.49/configure.in 2008-12-18 18:07:00.000000000 +0100
@@ -3,7 +3,7 @@
dnl -- This file is generated by y2autoconf 2.17.6 - DO NOT EDIT! --
dnl (edit configure.in.in instead)
-AC_INIT(yast2-installation, 2.17.47, http://bugs.opensuse.org/, yast2-installation)
+AC_INIT(yast2-installation, 2.17.48, http://bugs.opensuse.org/, yast2-installation)
dnl Check for presence of file 'RPMNAME'
AC_CONFIG_SRCDIR([RPMNAME])
@@ -18,7 +18,7 @@
AM_INIT_AUTOMAKE(tar-ustar -Wno-portability)
dnl Important YaST2 variables
-VERSION="2.17.47"
+VERSION="2.17.48"
RPMNAME="yast2-installation"
MAINTAINER="Lukas Ocilka "
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/control/docs/control-section.xml new/yast2-installation-2.17.49/control/docs/control-section.xml
--- old/yast2-installation-2.17.48/control/docs/control-section.xml 2008-12-15 14:13:02.000000000 +0100
+++ new/yast2-installation-2.17.49/control/docs/control-section.xml 2008-12-18 18:03:05.000000000 +0100
@@ -1519,4 +1519,7 @@
<emphasis>ProductControl::GetTranslatedText (text_id)</emphasis> call.</para>
</section>
</section>
+
+ http://www.w3.org/2001/XInclude"/>
</section>
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/control/docs/examples/update-difffileformat.xml new/yast2-installation-2.17.49/control/docs/examples/update-difffileformat.xml
--- old/yast2-installation-2.17.48/control/docs/examples/update-difffileformat.xml 1970-01-01 01:00:00.000000000 +0100
+++ new/yast2-installation-2.17.49/control/docs/examples/update-difffileformat.xml 2008-12-18 17:52:12.000000000 +0100
@@ -0,0 +1,142 @@
+
+<?xml version="1.0"?>
+http://www.suse.com/1.0/yast2ns"
+ xmlns:config="http://www.suse.com/1.0/configns">
+ <!-- .mo-file must be in installation tarball -->
+ <textdomain>OES</textdomain>
+ <!-- these options override base product's ones -->
+ <globals>
+
+ </globals>
+ <software>
+ auto
+ </software>
+ <partitioning>
+ false
+ 10G
+ </partitioning>
+ <network>
+ false
+ laptop
+ </network>
+ <!-- base product's list is preserved, these are appended -->
+
+ printer
+
+ <proposals config:type="list">
+<!-- put proposals for standalone product installation here -->
+ </proposals>
+<!-- workflow for standalone product installation -->
+ <workflows config:type="list">
+ <workflow>
+ <defaults>
+ <archs>all</archs>
+ </defaults>
+ <label>Preparation</label>
+ <!-- mode and stage must be set this way -->
+ <mode>installation</mode>
+ <stage>normal</stage>
+ <modules config:type="list">
+ <module>
+ <label>License Agreement</label>
+ <name>license</name>
+ no
+ yes
+ </module>
+ </modules>
+ </workflow>
+ </workflows>
+ <!-- stuff for installation together with base products -->
+ <update>
+ <proposals config:type="list">
+ <proposal>
+ <label>OES Installation Settings</label>
+ <mode>installation,demo,autoinstallation</mode>
+ <stage>initial</stage>
+ <name>initial</name>
+ no
+
+ module_1
+ module_2
+
+
+ module_3
+ module_4
+
+
+
+ <replace>old_module</replace>
+
+ module_5
+ module_6
+
+
+
+ </proposal>
+ </proposals>
+ <workflows config:type="list">
+ <workflow>
+ <defaults>
+ <archs>all</archs>
+ no
+ no
+ </defaults>
+ <mode>installation</mode>
+ <stage>initial</stage>
+
+ <module>
+ <heading>yes</heading>
+ <label>OES configuration</label>
+ </module>
+ <module>
+ <label>Perform Installation</label>
+ <name>a1_netsetup</name>
+ </module>
+ <module>
+ <label>Perform Installation</label>
+ <name>a2_netprobe</name>
+ </module>
+
+
+ finish
+
+
+
+ <before>perform</before>
+ <modules config:type="list">
+ <module>
+ <label>Perform Installation</label>
+ <name>i1_netprobe</name>
+ </module>
+ </modules>
+
+
+
+
+ <replace>language</replace>
+ <modules config:type="list">
+ <module>
+ <label>Perform Installation</label>
+ <name>r1_language</name>
+ </module>
+ </modules>
+
+
+ </workflow>
+ </workflows>
+
+
+ <module>before_chroot_1</module>
+ <module>before_chroot_2</module>
+
+
+ <module>after_chroot_1</module>
+ <module>after_chroot_2</module>
+
+
+ <module>before_umount_1</module>
+ <module>before_umount_2</module>
+
+
+ </update>
+</productDefines>
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/control/docs/examples/update-oes-example.xml new/yast2-installation-2.17.49/control/docs/examples/update-oes-example.xml
--- old/yast2-installation-2.17.48/control/docs/examples/update-oes-example.xml 1970-01-01 01:00:00.000000000 +0100
+++ new/yast2-installation-2.17.49/control/docs/examples/update-oes-example.xml 2008-12-18 17:52:02.000000000 +0100
@@ -0,0 +1,122 @@
+
+<?xml version="1.0"?>
+http://www.suse.com/1.0/yast2ns"
+ xmlns:config="http://www.suse.com/1.0/configns">
+<textdomain>OES</textdomain>
+<network>
+ true
+ false
+</network>
+<proposals config:type="list">
+ <proposal>
+ <name>oes</name>
+ <stage>continue,normal</stage>
+ <mode>installation</mode>
+
+ oes-ldap
+ imanager
+ lifeconsole
+ linux-user-mgmt
+ eguide
+ novell-samba
+ ifolder2
+ ifolder
+ ifolderwebaccess
+ iprint
+ nss
+ netstorage
+ novell-quickfinder
+ novell-vo
+ ncs
+ ncpserver
+ sms
+
+ </proposal>
+</proposals>
+<workflows config:type="list">
+ <workflow>
+ <label>Preparation</label>
+ <defaults>
+ <archs>all</archs>
+ </defaults>
+ <mode>installation</mode>
+ <stage>normal</stage>
+ <modules config:type="list">
+ <module>
+ <label>License Agreement</label>
+ <name>inst_license</name>
+ no
+ yes
+ </module>
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_check_cert</name>
+ no
+ yes
+ </module>
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_proposal</name>
+ <arguments>false,false,`product</arguments>
+ no
+ yes
+ </module>
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_oes</name>
+ yes
+ yes
+ </module>
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_oes_congratulate</name>
+ no
+ yes
+ </module>
+ </modules>
+ </workflow>
+</workflows>
+<update>
+ <workflows config:type="list">
+ <workflow>
+ <defaults>
+ <archs>all</archs>
+ no
+ no
+ </defaults>
+ <stage>continue</stage>
+ <mode>installation</mode>
+
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_oes_congratulate</name>
+ </module>
+
+
+
+ <before>suseconfig</before>
+ <modules config:type="list">
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_check_cert</name>
+ </module>
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_edirectory</name>
+ </module>
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_proposal</name>
+ <arguments>false,true,`product</arguments>
+ </module>
+ <module>
+ <label>OES Configuration</label>
+ <name>inst_oes</name>
+ </module>
+ </modules>
+
+
+ </workflow>
+ </workflows>
+ </update>
+</productDefines>
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/control/docs/Makefile.am new/yast2-installation-2.17.49/control/docs/Makefile.am
--- old/yast2-installation-2.17.48/control/docs/Makefile.am 2008-12-15 14:13:02.000000000 +0100
+++ new/yast2-installation-2.17.49/control/docs/Makefile.am 2008-12-18 18:03:47.000000000 +0100
@@ -13,7 +13,7 @@
pdf: control-doc.pdf
-html/index.html: control-doc.xml
+html/index.html: $(xml_files)
XML_CATALOG_FILES=@XML_CATALOG@ \
@XSLTPROC@ @XSLTPROC_FLAGS@ --xinclude \
@STYLESHEET_HTML@ $<
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/control/docs/Makefile.in new/yast2-installation-2.17.49/control/docs/Makefile.in
--- old/yast2-installation-2.17.48/control/docs/Makefile.in 2008-12-16 12:11:39.000000000 +0100
+++ new/yast2-installation-2.17.49/control/docs/Makefile.in 2008-12-18 18:07:04.000000000 +0100
@@ -531,7 +531,7 @@
pdf: control-doc.pdf
-html/index.html: control-doc.xml
+html/index.html: $(xml_files)
XML_CATALOG_FILES=@XML_CATALOG@ \
@XSLTPROC@ @XSLTPROC_FLAGS@ --xinclude \
@STYLESHEET_HTML@ $<
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/control/docs/update-section.xml new/yast2-installation-2.17.49/control/docs/update-section.xml
--- old/yast2-installation-2.17.48/control/docs/update-section.xml 1970-01-01 01:00:00.000000000 +0100
+++ new/yast2-installation-2.17.49/control/docs/update-section.xml 2008-12-18 18:00:43.000000000 +0100
@@ -0,0 +1,528 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!-- Section originally written by Jiri Srain /jsrain@suse.cz/ -->
+<section id="update">
+ <title>Add-on Product Installation Workflow Specification</title>
+ <section id="update-intro">
+ <title>Introduction</title>
+
+ <section id="update-intro-proddep">
+ <title>Product dependency</title>
+ <para>Everywhere, product B depends on product A, there is no dependency
+ related to product C. A, B and C are add-on products.</para>
+ </section>
+
+ <section id="update-intro-order">
+ <title>Order of updates of the workflow/wizard</title>
+ <para>If there are two add-on products which want to insert their steps
+ into the same location of the installation workflow (or proposal), they
+ are inserted in the same order as the products are added. A must be added
+ before B (otherwise adding B fails), steps of A are always prior to steps
+ of B.</para>
+ </section>
+
+ <section id="update-intro-items">
+ <title>Steps/Proposal Items Naming</title>
+ <para>In order to avoid collisions of internal names of proposal items or
+ sequence steps, all items should have its internal name prefixed by the
+ add-on product name.</para>
+ </section>
+
+ <section id="update-updposs">
+ <title>Update possibilities</title>
+
+ <section id="update-updposs-insert">
+ <title>Insert an item into proposal</title>
+ <para>Item is always added at the end of the proposal. Multiple
+ items are possible.</para>
+ </section>
+
+ <section id="update-updposs-remove">
+ <title>Remove an item from proposal</title>
+ <para>Specified item(s) are removed from proposal. Useful when
+ add-on product extends functionality of the base product. If
+ product B wants to remove an item of product A, must specify the
+ name of the product as well. Product C cannot remove items of
+ products A or B (and vice versa), product A cannot remove items
+ of product B.</para>
+ </section>
+
+ <section id="update-updposs-replace">
+ <title>Replace an item in proposal</title>
+ <para>Usable in the same cases as the case above. If an item has
+ been replaced by another item(s) of product A before applying
+ changes of product B, the item(s) of product A will be replaced
+ by item(s) of product B. Items of product C cannot be replaced by
+ items of product A or B (and vice versa), such combination of
+ products cannot be installed at the same time.</para>
+ </section>
+
+ <section id="update-updposs-insert">
+ <title>Insert steps to installation sequence</title>
+ <para>Before each step of base product installation, additional
+ step can be inserted (eg. another proposal). For the order of
+ additionally added steps, the same rules as for items of proposal
+ will be applied.</para>
+ </section>
+
+ <section id="update-updposs-append">
+ <title>Append steps to installation sequence</title>
+ <para>The steps can be appended at the end of installation
+ sequence.</para>
+ </section>
+
+ <section id="update-updposs-remoandrepl">
+ <title>Remove and replace steps in installation sequence</title>
+ <para>The same rules for removing and replacing steps of the
+ installation workflow as for proposal items will be applied.</para>
+ </section>
+
+ <section id="update-updposs-instfinish">
+ <title>Add, remove, replace items in inst_finish.ycp</title>
+ <para>The same rules as for steps of the installation workflow are
+ valid here. There will be some points in the inst_finish where
+ performing additional actions makes sense (at least one before
+ moving SCR to chroot and one after).</para>
+ </section>
+
+ <section id="update-updposs-replaceworkflow">
+ <title>Replace whole second-stage workflow</title>
+ <para>Add-on product may replace whole second stage of installation.
+ It should be used only in rare cases, as there is no possibility to
+ merge two workflows completely written from scratch. If a product
+ replaces the workflow, all changes of all products which replaced it
+ before (in case of installation of multiple products) are gone.
+ Add-on products selected after this product update the new workflow
+ (which may not work, as the steps usually have different naming).
+ This is perfectly OK if there are dependencies between add-on
+ products.</para>
+ <para>The workflow can be replaced only for specified installation
+ mode. If it is replaced, it must be replaced for all
+ architectures.</para>
+ </section>
+
+ <section id="update-updposs-addproposal">
+ <title>Adding a new proposal</title>
+ <para>New proposal can be added, as the proposal handling routines
+ are generic. The information which is for current product in control.xml
+ file has to be provided, and the proposal must be added as a step into
+ the installation workflow. Basically, adding proposal has two
+ steps:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>defining the proposal (name, items,...)</para>
+ </listitem>
+
+ <listitem>
+ <para>adding a new step to the workflow referring to the new
+ added proposal</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="update-updposs-replaceproposal">
+ <title>Replace or remove whole proposal</title>
+ <para>Is possible as replacing or removing a step of the installation
+ workflow.</para>
+ </section>
+ </section>
+
+ <section id="update-filelayout">
+ <title>File layout</title>
+ <section id="update-filelayout-addon">
+ <title>Add-on Product CD</title>
+ <para>There will be following files in the root directory of the
+ add-on product's CD:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>servicepack.tar.gz – tarball with files which are
+ needed for the installation, both together with base
+ product and separatelly. Special files inside this
+ tarball:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>installation.xml – the control file of the
+ add-on product</para>
+ </listitem>
+ <listitem>
+ <para>the whole tarball or installation.xml can be
+ missing if add-on product doesn't provide any custom
+ installer, in this case, only its packages are added
+ to the package manager dialog, and packages/patterns/...
+ required by the product are selected by the
+ solver</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>(optional) setup.sh – script which starts the
+ installation automatically once the CD is in the
+ drive</para>
+ </listitem>
+
+ <listitem>
+ <para>(optional) files needed to make the CD bootable
+ (kernel, initrd, isolinux,...)</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="update-filelayout-wkfadapt">
+ <title>Workflow Adaptation</title>
+ <para>There is only a single control file to describe both an
+ add-on and standalone product installation. It is called
+ installation.xml. In principle, it contains a diff description
+ containing the changes to be applied to the installation workflow
+ plus a workflow, which is used for standalone product installation.
+ The reason why both installation methods are stored in a single
+ file is that the product features has to be shared as well as some
+ proposals and clients can be reused.</para>
+
+ <para>The proposals which are defined for standalone installation
+ are also available for the installation together with the base
+ product. They don't have to be defined twice.</para>
+
+ <para>The files are located in the top directory of the add-on
+ product installation source.</para>
+ </section>
+ </section>
+
+ <section id="update-difffileformat">
+ <title>Diff File Format</title>
+ <para>Because there are no really usable open source XML diff tools (the
+ existing ones are typically written in Java), we define a special purpose
+ file format aimed to cover the cases as described in the previous
+ chapter.</para>
+
+ <para>In principle, the format is a list of directives to be applied to
+ the existing control.xml. In principle, the file is a control file
+ defining its own proposals, workflows etc. The control file has a special
+ section, which defines changes to the existing workflow and
+ proposals.</para>
+
+ <programlisting>
+ http://www.w3.org/2001/XInclude"/>
+ </programlisting>
+
+ </section>
+
+ <section id="update-textdomain">
+ <title>Setting a text domain</title>
+ <para>Text domain is important for YaST to handle translations
+ properly. The appropriate set of .mo-files must be present to have
+ the texts related to the control file translated.</para>
+
+ <programlisting>
+ <textdomain>OES</textdomain>
+ </programlisting>
+ </section>
+
+ <section id="update-standaloneinst">
+ <title>Defining proposals and workflow for standalone installation</title>
+ <para>The proposals are defined the same way as for the base product.
+ The workflow for the standalone installation must have the mode and stage
+ set</para>
+
+ <programlisting>
+ <mode>installation</mode>
+ <stage>normal</stage>
+ </programlisting>
+ </section>
+
+ <section id="update-proposalmodif">
+ <title>Proposal modification</title>
+ <para>The label of the proposal can be modified. The mode, stage, and
+ proposal name has to be specified, other options (enable_skip,
+ architecture) are optional. The modes, stages, and architectures
+ do not</para>
+
+ <programlisting>
+ <proposal>
+ <label>OES Installation Settings</label>
+ <mode>installation,demo,autoinstallation</mode>
+ <stage>initial</stage>
+ <name>initial</name>
+ <enable_skip>no</enable_skip>
+ [.....]
+ </proposal>
+ </programlisting>
+ </section>
+
+ <section id="update-append">
+ <title>Appending an item at the end of proposal</title>
+ <para>Adding an item to a proposal is possible at the end only.
+ If the proposal has tabs, the items are added to a new created
+ tab.</para>
+
+ <programlisting>
+ <append_modules config:type="list">
+ <append_module>module_1</append_module>
+ <append_module>module_2</append_module>
+ </append_modules>
+ </programlisting>
+ </section>
+
+ <section id="update-removeproposal">
+ <title>Removing an item from a proposal</title>
+ <programlisting>
+ <remove_modules config:type="list">
+ <remove_module>module_3</remove_module>
+ <remove_module>module_4</remove_module>
+ </remove_modules>
+ </programlisting>
+ </section>
+
+ <section id="update-replaceproposal">
+ <title>Replacing an item of a proposal</title>
+ <para>The replacement is available in 1:N mode – one client is to be
+ replaced by one or more new clients. If you need M:N use remove and
+ replace together.</para>
+
+ <programlisting>
+ <replace_modules config:type="list">
+ <replace_module>
+ <replace>old_module</replace>
+ <new_modules config:type="list">
+ <new_module>module_5</new_module>
+ <new_module>module_6</new_module>
+ </new_modules>
+ </replace_module>
+ </replace_modules>
+ </programlisting>
+ </section>
+
+ <section id="update-workflowupdates">
+ <title>Workflow updates</title>
+ <para>The workflow to update is identified the same way as other
+ workflows. The archs, modes, and installation don't need tobe
+ alligned to the same groups as in the base product
+ workflows.</para>
+
+ <programlisting>
+ <workflow>
+ <defaults>
+ <archs>all</archs>
+ <enable_back>no</enable_back>
+ <enable_next>no</enable_next>
+ </defaults>
+ <mode>installation</mode>
+ <stage>initial</stage>
+ [...]
+ </workflow>
+ </programlisting>
+ </section>
+
+ <section id="update-append">
+ <title>Append steps to the end of installation sequence</title>
+
+ <programlisting>
+ <append_modules config:type="list">
+ <module>
+ <heading>yes</heading>
+ <label>OES configuration</label>
+ </module>
+ <module>
+ <label>Perform Installation</label>
+ <name>a1_netsetup</name>
+ </module>
+ <module>
+ <label>Perform Installation</label>
+ <name>a2_netprobe</name>
+ </module>
+ [...]
+ </append_modules>
+ </programlisting>
+ </section>
+
+ <section id="update-insert">
+ <title>Insert steps to installation sequence</title>
+
+ <programlisting>
+ <insert_modules config:type="list">
+ <insert_module>
+ <before>perform</before>
+ <modules config:type="list">
+ <module>
+ <label>Perform Installation</label>
+ <name>i1_netprobe</name>
+ </module>
+ [...]
+ </modules>
+ </insert_module>
+ </insert_modules>
+ </programlisting>
+ </section>
+
+ <section id="update-removesteps">
+ <title>Remove steps from installation sequence</title>
+
+ <programlisting>
+ <remove_modules config:type="list">
+ <remove_module>finish</remove_module>
+ [...]
+ </remove_modules>
+ </programlisting>
+ </section>
+
+ <section id="update-replacesteps">
+ <title>Replace steps in installation sequence</title>
+
+ <programlisting>
+ <replace_modules config:type="list">
+ <replace_module>
+ <replace>language</replace>
+ <modules config:type="list">
+ <module>
+ <label>Perform Installation</label>
+ <name>r1_language</name>
+ </module>
+ [...]
+ </modules>
+ </replace_module>
+ </replace_modules>
+ </programlisting>
+ </section>
+
+ <section id="update-instfinish">
+ <title>Add items in inst_finish.ycp</title>
+ <para>In CODE 10, the last step of an installation commonly known
+ as inst_finish has been modularized, so it's possible to control
+ the clients started at the end of the 1st stage. In principle, this
+ phase runs in a chroot environment – all system access is done via
+ chrooted process.</para>
+
+ <para>There are 3 cases that an add-on product can modify the workflow...</para>
+
+ <section id="update-instfinish-beforechroot">
+ <title>Before chroot</title>
+
+ <programlisting>
+ <inst_finish_stages config:type="list">
+ <before_chroot>
+ <label>Copy Theme</label>
+ <steps config:type="list">
+ <step>copy_theme</step>
+ [...]
+ </steps>
+ </before_chroot>
+ </inst_finish_stages>
+ </programlisting>
+ </section>
+
+ <section id="update-instfinish-chroot">
+ <title>Running in chroot</title>
+
+ <programlisting>
+ <inst_finish_stages config:type="list">
+ <chroot>
+ <label>Update Configuration</label>
+ <steps config:type="list">
+ <step>pkg</step>
+ [...]
+ </steps>
+ </chroot>
+ </inst_finish_stages>
+ </programlisting>
+ </section>
+
+ <section id="update-instfinish-beforeumount">
+ <title>Before unmounting the system</title>
+
+ <programlisting>
+ <inst_finish_stages config:type="list">
+ <before_umount>
+ <label>Disconnect Network Disks</label>
+ <steps config:type="list">
+ <step>iscsi_disconnect</step>
+ [...]
+ </steps>
+ </before_umount>
+ </inst_finish_stages>
+ </programlisting>
+ </section>
+
+ <para>All new steps are added at the end of the current list in the
+ particular inst_finish workflow. It is not possible to remove any
+ other inst_finish clients or replace them.</para>
+ </section>
+
+ <section id="update-replaceworkflow">
+ <title>Replace whole second-stage workflow</title>
+ <para>To replace a workflow, just create workflows as in base
+ product control file. The important is that the stage of the
+ workflow is set to</para>
+
+ <programlisting>
+ <stage>continue</stage>
+ </programlisting>
+
+ <para>and the mode is set for the specified mode.</para>
+ </section>
+
+ <section id="update-algorithm">
+ <title>Algorith for Adapting Workflow</title>
+ <para>The algorithm is rather straightforward. Every time, remove
+ is applied first, then replace and the last step is add. This is
+ done per product, so first the changes by product A are applied,
+ then by product B etc.</para>
+ </section>
+
+ <section id="update-algorithm-features">
+ <title>Product Features</title>
+ <para>One of the most important data stored in the control.xml
+ file are the values to influence the behavior of YaST code,
+ like proposals etc. The idea is the same as for workflow/proposal
+ adaptation: by redefining a value, the resulting values are
+ changed. Within YaST, the options are accessible via
+ ProductFeatures module. No new option groups can be defined.
+ Options which are defined by the base product, but not by the
+ add-on product, are kept unchanged (base product's value is
+ used).</para>
+
+ <programlisting>
+ <globals>
+ <additional_kernel_parameters></additional_kernel_parameters>
+ </globals>
+ [...]
+ <software>
+ <selection_type config:type="symbol">auto</selection_type>
+ </software>
+ </programlisting>
+ </section>
+
+ <section>
+ <title>AutoYaST profile generation</title>
+ <para>At the end of the installation, a profile for AutoYaST can be
+ generated. The profile will be generated using modules from the base
+ product and modules specified in the add-on product control
+ file.</para>
+
+ <programlisting>
+ <clone_modules config:type="list">
+ <clone_module>printer</clone_module>
+ [...]
+ </clone_modules>
+ </programlisting>
+ </section>
+
+ <section>
+ <title>Example of OES 1.0</title>
+ <para>The network code is instructed to force a static IP
+ address.</para>
+
+ <para>The control file contains steps for both standalone installation
+ and installation together with the base product. In the standalone
+ installation workflow, selecting and installing packages is missing,
+ these steps need to be prepended to the workflow.</para>
+
+ <programlisting>
+ http://www.w3.org/2001/XInclude"/>
+ </programlisting>
+ </section>
+ </section>
+</section>
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-installation-2.17.48/VERSION new/yast2-installation-2.17.49/VERSION
--- old/yast2-installation-2.17.48/VERSION 2008-12-17 14:44:02.000000000 +0100
+++ new/yast2-installation-2.17.49/VERSION 2008-12-18 18:08:44.000000000 +0100
@@ -1 +1 @@
-2.17.48
+2.17.49
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Remember to have fun...
--
To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-commit+help@opensuse.org