Git-Url: 
http://git.frugalware.org/gitweb/gitweb.cgi?p=fvbe.git;a=commitdiff;h=caede9c3a5b230cb78c8e5ed185bdac5a4081a28

commit caede9c3a5b230cb78c8e5ed185bdac5a4081a28
Author: DeX77 <[email protected]>
Date:   Thu May 25 00:40:39 2017 +0200

+ add calamares config for frugalware frugalware/fvbe#1

diff --git a/calamares-config/modules/locale.conf 
b/calamares-config/modules/locale.conf
new file mode 100644
index 0000000..6cef03d
--- /dev/null
+++ b/calamares-config/modules/locale.conf
@@ -0,0 +1,7 @@
+---
+region:                     "America"
+zone:                       "New_York"
+
+# GeoIP settings. Leave commented out to disable GeoIP.
+#localeGenPath:             "/etc/locale.gen"
+geoipUrl:                  "freegeoip.net"
diff --git a/calamares-config/modules/mount.conf 
b/calamares-config/modules/mount.conf
new file mode 100644
index 0000000..d8f8fb8
--- /dev/null
+++ b/calamares-config/modules/mount.conf
@@ -0,0 +1,22 @@
+---
+extraMounts:
+    - device: proc
+      fs: proc
+      mountPoint: /proc
+    - device: sys
+      fs: sysfs
+      mountPoint: /sys
+    - device: /dev
+      mountPoint: /dev
+      options: bind
+    - device: tmpfs
+      fs: tmpfs
+      mountPoint: /run
+    - device: /run/udev
+      mountPoint: /run/udev
+      options: bind
+
+extraMountsEfi:
+    - device: efivarfs
+      fs: efivarfs
+      mountPoint: /sys/firmware/efi/efivars
diff --git a/calamares-config/modules/removeuser.conf 
b/calamares-config/modules/removeuser.conf
new file mode 100644
index 0000000..9c865b7
--- /dev/null
+++ b/calamares-config/modules/removeuser.conf
@@ -0,0 +1,2 @@
+---
+username: guest
diff --git a/calamares-config/modules/services.conf 
b/calamares-config/modules/services.conf
new file mode 100644
index 0000000..b978550
--- /dev/null
+++ b/calamares-config/modules/services.conf
@@ -0,0 +1,15 @@
+---
+#systemd services and targets are enabled in this precise order
+
+services:
+  - name: "NetworkManager"  #name of the service file
+    mandatory: false        #true=> if enabling fails the installer errors out 
and quits
+                            #false=>if enabling fails print warning to console 
and continue
+  - name: "org.cups.cupsd"
+    mandatory: false
+
+targets:
+  - name: "graphical"
+    mandatory: true
+
+disable: []
diff --git a/calamares-config/modules/unpackfs.conf 
b/calamares-config/modules/unpackfs.conf
new file mode 100644
index 0000000..91eca93
--- /dev/null
+++ b/calamares-config/modules/unpackfs.conf
@@ -0,0 +1,5 @@
+---
+unpack:
+    -   source: "/dev/mapper/live-base"
+        sourcefs: "ext4"
+        destination: ""
diff --git a/calamares-config/modules/welcome.conf 
b/calamares-config/modules/welcome.conf
new file mode 100644
index 0000000..921ee6d
--- /dev/null
+++ b/calamares-config/modules/welcome.conf
@@ -0,0 +1,19 @@
+---
+showSupportUrl:         true
+showKnownIssuesUrl:     false
+showReleaseNotesUrl:    false
+
+requirements:
+    requiredStorage:    3.0
+    requiredRam:        0.5
+    internetCheckUrl:   http://google.com
+    check:
+        - storage
+        - ram
+        - power
+        - internet
+        - root
+    required:
+        - storage
+        - ram
+        - root
diff --git a/calamares-config/settings.conf b/calamares-config/settings.conf
new file mode 100644
index 0000000..dc5a82f
--- /dev/null
+++ b/calamares-config/settings.conf
@@ -0,0 +1,116 @@
+# Configuration file for Calamares
+# Syntax is YAML 1.2
+---
+# Modules can be job modules (with different interfaces) and QtWidgets view 
modules.
+# They could all be placed in a number of different paths.
+# "modules-search" is a list of strings, each of these can either be a full 
path to a
+# directory or the keyword "local".
+# "local" means LIBDIR/calamares/modules with settings in 
SHARE/calamares/modules or
+# /etc/calamares/modules.
+# YAML: list of strings.
+modules-search: [ local ]
+
+# Instances section. This section is optional, and it defines custom instances 
for
+# modules of any kind. An instance entry has an instance name, a module name, 
and
+# a configuration file name.
+# The primary goal of this mechanism is to allow loading multiple instances of 
the
+# same module, with different configuration. If you don't need this, the 
instances
+# section can safely be left empty.
+# Module name plus instance name makes an instance key, e.g. 
"webview@owncloud",
+# where "webview" is the module name (for the webview viewmodule) and 
"owncloud"
+# is the instance name, which loads a configuration file named "owncloud.conf" 
from
+# any of the configuration file paths, including the webview module directory.
+# This instance key can then be referenced in the sequence section.
+# For all modules without a custom instance specification, a default instance 
is
+# generated automatically by Calamares. Therefore a statement such as 
"webview" in
+# the sequence section automatically implies an instance key of 
"webview@webview"
+# even without explicitly defining this instance, and the configuration file 
for
+# this default instance "<modulename>@<modulename>" is always assumed to be
+# "<modulename>.conf".
+# For more information on running module instances, run Calamares in debug mode
+# and check the Modules page in the Debug information interface.
+# YAML: list of maps of string:string key-value pairs.
+
+#instances:
+#- id:       owncloud
+#  module:   webview
+#  config:   owncloud.conf
+
+# Sequence section. This section describes the sequence of modules, both
+# viewmodules and jobmodules, as they should appear and/or run.
+# A jobmodule instance key (or name) can only appear in an exec phase, whereas
+# a viewmodule instance key (or name) can appear in both exec and show phases.
+# There is no limit to the number of show or exec phases. However, the same 
module
+# instance key should not appear more than once per phase, and deployers should
+# take notice that the global storage structure is persistent throughout the
+# application lifetime, possibly influencing behavior across phases.
+# A show phase defines a sequence of viewmodules (and therefore pages). These
+# viewmodules can offer up jobs for the execution queue.
+# An exec phase displays a progress page (with brandable slideshow). This 
progress
+# page iterates over the modules listed in the *immediately preceding* show 
phase,
+# and enqueues their jobs, as well as any other jobs from jobmodules, in the 
order
+# defined in the current exec phase.
+# It then executes the job queue and clears it. If a viewmodule offers up a job
+# for execution, but the module name (or instance key) isn't listed in the
+# immediately following exec phase, this job will not be executed.
+# WARNING: when upgrading from Calamares 1.1, this section requires manual
+# intervention. There are no fixed prepare/install/postinstall phases any more,
+# and all limitations on the number of phases, number of pages, and number of
+# instances are lifted.
+# YAML: list of lists of strings.
+sequence:
+- show:
+  - welcome
+  - locale
+  - keyboard
+  - partition
+  - users
+  - summary
+- exec:
+  - partition
+  - mount
+  - unpackfs
+  - machineid
+  - fstab
+  - locale
+  - keyboard
+  - localecfg
+  - users
+  - displaymanager
+  - networkcfg
+  - hwclock
+  - services
+  - removeuser
+  - grubcfg
+  - bootloader
+  - umount
+- show:
+  - finished
+
+# A branding component is a directory, either in SHARE/calamares/branding or in
+# /etc/calamares/branding (the latter takes precedence). The directory must 
contain a
+# YAML file branding.desc which may reference additional resources (such as 
images) as
+# paths relative to the current directory.
+# A branding component can also ship a QML slideshow for execution pages, 
along with
+# translation files.
+# Only the name of the branding component (directory) should be specified 
here, Calamares
+# then takes care of finding it and loading the contents.
+# YAML: string.
+branding: frugalware
+
+# If this is set to true, Calamares will show an "Are you sure?" prompt right 
before
+# each execution phase, i.e. at points of no return. If this is set to false, 
no prompt
+# is shown.
+# Default is false.
+# YAML: boolean.
+prompt-install: false
+
+# If this is set to true, Calamares will execute all target environment 
commands in the
+# current environment, without chroot. This setting is considered 
experimental, and it
+# should only be used when setting up Calamares as a post-install 
configuration tool, as
+# opposed to a full operating system installer.
+# Some official Calamares modules are not expected to function with this 
setting.
+# Packagers beware, here be dragons.
+# Default is false.
+# YAML: boolean.
+dont-chroot: false
_______________________________________________
Frugalware-git mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-git

Reply via email to