Hello community,
here is the log from the commit of package yast2-installation for openSUSE:Factory checked in at 2016-11-03 12:56:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-installation (Old)
and /work/SRC/openSUSE:Factory/.yast2-installation.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-installation"
Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-installation/yast2-installation.changes 2016-10-22 13:05:25.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-installation.new/yast2-installation.changes 2016-11-03 12:56:42.000000000 +0100
@@ -1,0 +2,11 @@
+Mon Oct 31 13:23:38 UTC 2016 - lslezak@suse.cz
+
+- Added support for read-only proposal modules (fate#321739)
+- 3.2.6
+
+-------------------------------------------------------------------
+Thu Oct 27 15:09:58 CEST 2016 - shundhammer@suse.de
+
+- Documentation for subvolumes in control.xml (fate#321737)
+
+-------------------------------------------------------------------
Old:
----
yast2-installation-3.2.5.tar.bz2
New:
----
yast2-installation-3.2.6.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-installation.spec ++++++
--- /var/tmp/diff_new_pack.tW6pOW/_old 2016-11-03 12:56:43.000000000 +0100
+++ /var/tmp/diff_new_pack.tW6pOW/_new 2016-11-03 12:56:43.000000000 +0100
@@ -17,7 +17,7 @@
Name: yast2-installation
-Version: 3.2.5
+Version: 3.2.6
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++++++ yast2-installation-3.2.5.tar.bz2 -> yast2-installation-3.2.6.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-installation-3.2.5/README.md new/yast2-installation-3.2.6/README.md
--- old/yast2-installation-3.2.5/README.md 2016-10-20 15:35:29.000000000 +0200
+++ new/yast2-installation-3.2.6/README.md 2016-11-02 11:00:06.000000000 +0100
@@ -3,7 +3,7 @@
[![Travis Build](https://travis-ci.org/yast/yast-installation.svg?branch=master)](https://travis-ci.org/yast/yast-installation)
[![Jenkins Build](http://img.shields.io/jenkins/s/https/ci.opensuse.org/yast-installation-master.svg)](https://ci.opensuse.org/view/Yast/job/yast-installation-master/)
-
+[![Coverage Status](https://coveralls.io/repos/github/yast/yast-installation/badge.svg?branch=master)](https://coveralls.io/github/yast/yast-installation?branch=master)
Description
============
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-installation-3.2.5/doc/control-file.md new/yast2-installation-3.2.6/doc/control-file.md
--- old/yast2-installation-3.2.5/doc/control-file.md 2016-10-20 15:35:29.000000000 +0200
+++ new/yast2-installation-3.2.6/doc/control-file.md 2016-11-02 11:00:06.000000000 +0100
@@ -65,8 +65,10 @@
- Partitioning
- Integrates flexible partitioning into configuration file, instead of
- the separate file currently used.
+ This is to customize disk usage, including minimum and maximum useful size
+ of the root filesystem, what filesytem type to use, whether or not to use
+ LVM and encryption, and what subvolumes to create if Btrfs is used on the
+ root filesystem.
- Scripting and Hooks
@@ -127,8 +129,15 @@
developers the ability to change the installation behavior and customize
various settings without the need to change and re-build YaST packages.
-The control files for some SUSE products are maintained at
-yast2-installation source tree in directory `control`.
+This way it is possible to define different behavior and different installation
+defaults in SLE and openSUSE products.
+
+The control files for SUSE products are maintained at specific Git
+repositories (e.g. for [SLES](https://github.com/yast/skelcd-control-SLES/blob/master/control/control.SLES...),
+[SLED](https://github.com/yast/skelcd-control-SLED/blob/master/control/control.SLED...)
+or [openSUSE](https://github.com/yast/skelcd-control-openSUSE/blob/master/control/control....)
+).
+
Configuration
-------------
@@ -192,7 +201,7 @@
- arguments: The arguments for the module is a comma separated
list which can accept booleans and symbols.
- - execute: If it is needed to call script that does not start with
+ - execute: If it is needed to call script that does not start with
*inst_* or you need to call the same script several times with
different *name* parameter.
@@ -266,30 +275,47 @@
```xml
- <proposal>
- <type>network</type>
- <stage>continue,normal</stage>
-
- lan
- dsl
- isdn
- modem
- proxy
- remote
-
- </proposal>
+<proposal>
+ <label>Installation Settings</label>
+ <mode>installation</mode>
+ <stage>initial</stage>
+ <name>initial</name>
+ inst_initial
+ no
+
+
+ <name>bootloader</name>
+ 20
+
+
+ <name>hwinfo</name>
+ 80
+
+ ...
+
+</proposal>
+```
+
+Each proposal definition can contain these values:
+
+```xml
+
+ <name>module_name</name>
+ 50
+ true
+
```
-The proposal in the above listing is displayed in the so called
-*continue* mode which is the second phase of the installation. The
-proposal consists of different configuration options which are controled
-using a special API.
-
-Currently, proposals names and captions are fixed and cannot be changed. It
-is not possible to create a special proposal screen, instead those
-available should be used: *network*, *hardware*, *service*. All proposal script
-names are listed without *_proposal* suffix. If a *proposed_module* is called
-*example*, then installer looks for *example_proposal* script.
+Details:
+
+- `name` (string) - proposal client name without the `_proposal` suffix
+ (the code actually allows writing it but that makes the definitions longer
+ and less readable).
+- `presentation_order` (integer, optional) - the number defines the display order
+ in the proposal, the absolute value is not important, it depends on the relative
+ value when compared against the other proposal modules.
+- `read_only` (boolean, optional) - the module is treated as read only and
+ any user interaction with the proposal module is disabled.
In the workflow, the proposals are called as any workflow step with an
additional argument identifying the proposal screen to be started.
@@ -510,93 +536,6 @@
one entry for one file or directory; files are optional and are
copied if they exist; missing files are skipped
-### Automatic Configuration
-
-This is another feature defined in *globals* section. *Automatic
-Configuration* is called via the script *inst\_automatic\_configuration*
-at the end of the second stage installation. Having the configuration in
-control file enables this function for another modes and makes it very
-well configurable.
-
-This is an example of AC setup:
-
-```xml
- http://www.suse.com/1.0/yast2ns"
- xmlns:config="http://www.suse.com/1.0/configns">
- <globals>
-
- <!-- List of steps in AC -->
-
-
- <!-- One step definition -->
-
- ac_1
- <type>scripts</type>
-
- initialization
- hostname
- netprobe
- rpmcopy_secondstage
-
- <icon>yast-lan</icon>
-
-
-
- ac_3
- <type>proposals</type>
-
- x11
- printer
- sound
- tv
-
- <icon>yast-hwinfo</icon>
-
-
-
- </globals>
-
- <texts>
-
- <!-- Label used during AC, uses "text_id" from "ac_step" -->
- <label>Initialization...</label>
- <label>Configuring hardware...</label>
-
- </texts>
- </productDefines>
-```
-
-AC setup *automatic\_configuration* consists of list of several
-*ac\_step* definitions. On definition for one AC step. These steps can
-be compared to sets of scripts or sets of installation proposals, e.g.,
-*network proposal* that consists of *lan*, *modem*, ... and *firewall*
-proposals which might depend on each others proposals.
-
-Every single *ac\_step* consists of
-
-- *text\_id* - which is the very same ID as used in
- [texts](#control_texts) (you have to define the AC label there).
-
-- *type* - defines how the AC step items will be handled. Possible
- values are *scripts* or *proposals*. More types cannot be mixed
- within one AC step. All *scripts* are called only once one by one,
- all *proposals* in one AC step are called first with *MakeProposal*
- parameter then again all with *Write* parameter.
-
-- *ac\_items* - is a list of scripts or proposals each in a separate
- *ac\_item*.
-
- For scripts an *ac\_item* is a name of YaST client script without
- *inst\_* prefix, e.g., *firewall* would call *inst\_firewall*
- script.
-
- For proposals an *ac\_item* is a name of YaST proposal without
- *\_proposal* suffix, e.g., *firewall* would call
- *firewall\_proposal*.
-
-- *icon* - plain icon filename (from 22x22 directory) without suffix
- and without any explicit directory name, e.g., *yast-network*.
-
### Software
In the *software* section you can define how is the selection of
@@ -1016,327 +955,156 @@
### Partitioning
-If present, the partition proposal will be based on the data provided in
-the control file.
+#### Subvolumes
-#### Algorithm for Space Allocation
+This section is used to specify what subvolumes should be created if Btrfs is
+used for the root filesystem.
-Space allocation on a disk happens in the following order. First all
-partition get the size allocated that is determined by the size
-parameter of the partition description. If a disk cannot hold the sum of
-these sizes this disk is not considered for installation. If all demands
-by the size parameter are fulfilled and there is still space available
-on the disk, the partitions which have a parameter "percent" specified
-are increased until the size demanded by by "percent" is fulfilled. If
-there is still available space on the disk (this normally only can
-happen if the sum of all percent values are below 100), all partitions
-that are specified with a size of zero are enlarged as far as possible.
-If a "maxsize" is specified for a partition, all enlargement are only
-done up to the specified maxsize.
-
-If more than one of the available disks is eligible to hold a certain
-partition set, the disk is selected as follows. If there is a partition
-allocated on that disk that has its size specified by keywords "percent"
-or by "size=0" and does not have a "maxsize" value set then the desired
-size for this partition is considered to be unlimited. If a partition
-group contains a partition which an unlimited desired size, the disk
-that maximizes the partition size for the unlimited partitions is
-selected. If all partitions in a partition group are limited in size
-then the smallest disk that can hold the desired sizes of all partitions
-is selected for that partition group.
-
-If there are multiple partition groups the the partition group with the
-lowest number (means highest priority) get assigned its disk first.
-Afterward the partition group with the next priority gets assigned a the
-optimal disk from the so far unassigned disks.
-
-#### Configuration Options
-
-The following elements are global to all disks and partitions:
-
-Possible values
-: true|false
-
-Default value
-: true
-
-Description
-: If set to false the partition suggestion tries to use gaps on the
- disks or to re-use existing partitions. If set to true then the
- partition suggestion prefers removal of existing partitions.
-
-Possible values
-: true|false
-
-Default value
-: false
-
-Description
-: If set to false YaST2 will not remove some special partitions (e.g.
- 0x12 Compaq diagnostics, 0xde Dell Utility) if they exists on the
- disk even if prefer\_remove is set to true. If set to true YaST2
- will remove even those special partitions.
-
- > **Caution**
- >
- > Caution: Since some machines are not even bootable any more when
- > these partitions are removed one should really know what he does
- > when setting this to true
-
-Possible values
-: comma separated list of reiser, xfs, fat, vfat, ext2, ext3, jfs,
- ntfs, swap
-
-Default value
-: Empty list
-
-Description
-: Partitions that contain filesystems in that list are not deleted
- even if prefer\_remove is set to true.
-
-Possible values
-: comma separated list of possible partition ids
-
-Default value
-: Empty list
-
-Description
-: Partitions that have a partition id that is contained in the list
- are not deleted even if prefer\_remove is set to true.
-
-Possible values
-: comma separated list of possible partition numbers
-
-Default value
-: Empty list
-
-Description
-: Partitions that have a partition number that is contained in the
- list are not deleted even if prefer\_remove is set to true.
-
-To configure individual partitions and disks, a list element is used
-with its items describing how should the partitions be created and
-configured
+The *subvolumes* section is optional. If it is missing, a hard-coded list of
+default subvolumes is used. If the *subvolumes* section is there, but empty, no
+subvolumes are created.
-The attributes of such a partition are determined by several elements.
-These elements are described in more detail later.
+Each *subvolume* section has a mandatory *path* and optional *copy_on_write*
+and *archs* elements.
-> **Note**
->
-> If there is a blank or a equal sign (=) contained in an option value,
-> the values has to be surrounded by double quotes ("). Values that
-> describe sizes can be followed by the letters K, M, G. (K means
-> Kilobytes, M Megabytes and G Gigabytes).
-
-Example
-: \swap\
-
-Description
-: This entry describes the mount point of the partition. For a swap
- partition the special value "swap" has to be used.
-
-Example
-: \reiser\
-
-Description
-: This entry describes the filesystem type created on this partition.
- Possible Filesystem types are: reiser, ext2, ext3, xfs, vfat, jfs,
- swap If no filesystem type is given for a partition, reiserfs is
- used.
-
-Example
-: \reiser\
-
-Description
-: This entry describes the options given to the format command.
- Multiple options have to be separated by blanks. There must not be a
- blank between option letter and option value. This entry is
- optional.
-
-Example
-: \acl,user\_xattr\
-
-Description
-: This entry describes the options written to `/etc/fstab`. Multiple
- options have to be separated by comma. This entry is optional.
-
-Example
-: \