Changes between Version 15 and Version 16 of Obsolete/MovedToTree/PackageManagement/BuildingPackages

Timestamp:

May 28, 2013, 11:00:45 PM (11 years ago)

Author:

bonefish

Comment:

Add new package info attributes

Obsolete/MovedToTree/PackageManagement/BuildingPackages

@@ -74 +74 @@
  * `freshens`: A list of entities that are being freshened by this package (i.e. this package will patch one or more files of the package(s) that provide this entity). The list elements must have the `required_entity` format.
  * `replaces`: A list of entities that are being replaced by this package (used if the name of a package changes, or if a package has been split). The list elements must have the `entity_name` format.
-
+ * `global-settings-files`: A list of global settings file infos. The list elements must have the following format:
+{{{
+global_settings_file_info:      ::= path [ "keep-old" | "manual" | "mergeable" ]
+}}}
+   `path` is the relative path of the settings file, starting with "settings/". If no keyword is given after the path, the settings file is not included in the package. It will be created by the software or by the user. If a keyword is given, the settings file (a default version) is included in the package and it will be extracted on package activation. The keyword specifies what shall happen when the package is updated and a previous default version of the settings file has been modified by the user:
+   - "keep-old": Indicates that the software can read old settings files and the user-modified file should be kept.
+   - "manual": Indicates that the software may not be able to read an older file and the user may have to manually adjust it.
+   - "mergeable": Indicates that the file format is simple text and a three-way merge shall be attempted.
+ * `user-settings-files`: A list of user settings file infos. The list elements must have the following format:
+{{{
+user_settings_file_info:        ::= path [ "template" template_path ]
+}}}
+   `path` is the relative path of the settings file, starting with "settings/". It is not included in the package. However, if `template_path` is specified, it is a path to a file included in the package that can serve as a template for the settings file. It doesn't implies any automatic action on package activation, though.
+ * `users`: A list of specifications for Unix users the packaged software requires. The list elements must have the following format:
+{{{
+user:   ::= name [ "real-name" real_name ] "home" home_path [ "shell" shell_path ] [ "groups" group+ ]
+}}}
+   `name` is the name of the Unix user, `real_name`, if specified, the real name of the user, `home_path` the path to the user's home directory, `shell_path` the path to the user's shell, and `group` the name of a Unix group the users is a member of. If the respective components are not specified, `name` is also used as the user's real name, "/bin/bash" is the path of the user's shell, and the user will belong to the default user group.
+ * `groups`: A list of names of Unix groups the packaged software requires.
+ * `post-install-scripts`: A list of paths of files included in the package, which shall be executed on package activation. Each path must start with "boot/post-install/".
 
 === Version Strings ===