[app-misc/calamares-sabayon-base-modules] bump version to 1.11-r2

2018-06-24 12:05:05 +02:00
parent ad7d2842a5
commit 61387cff2e
10 changed files with 428 additions and 0 deletions
@@ -0,0 +1 @@
+DIST calamares-sabayon-base-modules-1.11.tar.gz 2791 BLAKE2B bb23609d371dc1e96e75a5d112cdcb476a85cbf2b318000b20ab2f0e07a4d40fa3b26148db70dc0c07d2f7730da31e2c79d580fcdf8caccdf9480e34c83e1ffb SHA512 4b062471e55751ec7be8073c721e1347b88b7a466cd5157429aaa79389062fe08e526bf2e443c262371035134c5d7a8d8366fe8ffbfc00af0b006afc0cde1aae
@@ -0,0 +1,26 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=5
+
+DESCRIPTION="Sabayon Official Calamares base modules"
+HOMEPAGE="http://www.sabayon.org/"
+SRC_URI="https://github.com/Sabayon/calamares-sabayon/archive/${PV}.tar.gz -> ${P}.tar.gz"
+LICENSE="CC-BY-SA-4.0"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE=""
+
+DEPEND="=app-admin/calamares-3.2*[networkmanager,upower]"
+RDEPEND="${DEPEND}"
+
+S="${WORKDIR}/calamares-sabayon-${PV}"
+
+src_install() {
+	insinto "/etc/calamares/"
+	doins -r "${FILESDIR}/${PN}-conf-${PVR}/"*
+	insinto "/usr/lib/calamares/modules/"
+	doins -r "${S}/"*
+	insinto "/etc/"
+	newins "${FILESDIR}/locale.gen" "locale.gen.bak"
+}
@@ -0,0 +1,27 @@
+---
+# Define which bootloader you want to use for EFI installations
+# Possible options are 'grub' and 'systemd-boot'.
+efiBootLoader: "grub"
+
+# systemd-boot configuration files settings, set kernel and initramfs file names
+# and amount of time before default selection boots
+kernel: "/boot/bzImage"
+img: "/boot/Initrd"
+fallback: "/boot/Initrd"
+timeout: "10"
+# Optionally set the menu entry name and kernel name to use in systemd-boot.
+# If not specified here, these settings will be taken from branding.desc.
+# bootloaderEntryName: "Generic GNU/Linux"
+# kernelLine: ", with Stable-Kernel"
+# fallbackKernelLine:  ", with Stable-Kernel (fallback initramfs)"
+
+# GRUB 2 binary names and boot directory
+# Some distributions (e.g. Fedora) use grub2-* (resp. /boot/grub2/) names.
+grubInstall: "grub2-install"
+grubMkconfig: "grub2-mkconfig"
+grubCfg: "/boot/grub/grub.cfg"
+# Optionally set the --bootloader-id to use for EFI. If not set, this defaults
+# to the bootloaderEntryName from branding.desc with problematic characters
+# replaced. If an efiBootloaderId is specified here, it is taken to already be a
+# valid directory name, so no such postprocessing is done in this case.
+# efiBootloaderId: "dirname"
@@ -0,0 +1,14 @@
+---
+# The name of the file to write X11 keyboard settings to
+# The default value is the name used by upstream systemd-localed.
+# Relative paths are assumed to be relative to /etc/X11/xorg.conf.d
+xOrgConfFileName: "/etc/X11/xorg.conf.d/00-keyboard.conf"
+
+# The path to search for keymaps converted from X11 to kbd format
+# Leave this empty if the setting does not make sense on your distribution.
+convertedKeymapPath: "/usr/share/keymaps/"
+
+# Write keymap configuration to /etc/default/keyboard, usually
+# found on Debian-related systems.
+# Defaults to true if nothing is set.
+writeEtcDefaultKeyboard: false
@@ -0,0 +1,138 @@
+---
+#
+# Which package manager to use, options are:
+#  - packagekit  - PackageKit CLI tool
+#  - zypp        - Zypp RPM frontend
+#  - yum         - Yum RPM frontend
+#  - dnf         - DNF, the new RPM frontend
+#  - urpmi       - Mandriva package manager
+#  - apt         - APT frontend for DEB and RPM
+#  - pacman      - Pacman
+#  - portage     - Gentoo package manager
+#  - entropy     - Sabayon package manager
+#  - dummy       - Dummy manager, only logs
+#
+backend: entropy
+
+# Often package installation needs an internet connection.
+# Since you may allow system installation without a connection
+# and want to offer **optional** package installation, it's
+# possible to have no internet, yet have this packages module
+# enabled in settings.
+#
+# You can skip the whole module when there is no internet
+# by setting *skip_if_no_internet* to true.
+#
+# You can run a package-manager specific update procedure
+# before installing packages (for instance, to update the
+# list of packages and dependencies); this is done only if there
+# is an internet connection. Set *update_db* to true to do so.
+skip_if_no_internet: false
+update_db: false
+
+#
+# List of maps with package operations such as install or remove.
+# Distro developers can provide a list of packages to remove
+# from the installed system (for instance packages meant only
+# for the live system).
+#
+# A job implementing a distro specific logic to determine other
+# packages that need to be installed or removed can run before
+# this one. Distro developers may want to install locale packages
+# or remove drivers not needed on the installed system.
+# Such a job would populate a list of dictionaries in the global
+# storage called "packageOperations" and that list is processed
+# after the static list in the job configuration (i.e. the list
+# that is in this configuration file).
+#
+# Allowed package operations are:
+#  - install, try_install: will call the package manager to
+#       install one or more packages. The install target will
+#       abort the whole installation if package-installation
+#       fails, while try_install carries on. Packages may be
+#       listed as (localized) names, or as (localized) package-data.
+#       See below for the description of the format.
+# - localInstall: this is used to call the package manager
+#       to install a package from a path-to-a-package. This is
+#       useful if you have a static package archive on the install media.
+# - remove, try_remove: will call the package manager to
+#       remove one or more packages. The remove target will
+#       abort the whole installation if package-removal fails,
+#       while try_remove carries on. Packages may be listed as
+#       (localized) names.
+#
+# There are two formats for naming packages: as a name or as package-data,
+# which is an object notation providing package-name, as well as pre- and
+# post-install scripts.
+#
+# Here are both formats, for installing vi. The first one just names the
+# package for vi (using the naming of the installed package manager), while
+# the second contains three data-items; the pre-script is run before invoking
+# the package manager, and the post-script runs once it is done.
+#
+# - install
+#   - vi
+#   - package: vi
+#     pre-script: touch /tmp/installing-vi
+#     post-script: rm -f /tmp/installing-vi
+#
+# The pre- and post-scripts are optional, but you cannot leave both out: using
+# "package: vi" with neither script option will trick Calamares into
+# trying to install a package named "package: vi", which is unlikely to work.
+#
+# Any package name may be localized; this is used to install localization
+# packages for software based on the selected system locale. By including
+# the string LOCALE in the package name, the following happens:
+#
+# - if the system locale is English (any variety), then the package is not
+#   installed at all,
+# - otherwise $LOCALE or ${LOCALE} is replaced by the **lower-cased** BCP47
+#   name of the **language** part of the selected system locale (not the
+#   country/region/dialect part), e.g. selecting *nl_BE* will use *nl*
+#   here.
+#
+# Take care that just plain LOCALE will not be replaced, so foo-LOCALE will
+# be left unchanged, while foo-$LOCALE will be changed. However, foo-LOCALE
+# **will** be removed from the list of packages, if English is selected.
+#
+# The following installs localizations for vi, if they are relevant; if
+# there is no localization, installation continues normally.
+#
+# - install
+#   - vi-$LOCALE
+#   - package: vi-${LOCALE}
+#     pre-script: touch /tmp/installing-vi
+#     post-script: rm -f /tmp/installing-vi
+#
+# When installing packages, Calamares will invoke the package manager
+# with a list of package names if it can; package-data prevents this because
+# of the scripts that need to run. In other words, this:
+#
+# - install:
+#   - vi
+#   - binutils
+#   - package: wget
+#     pre-script: touch /tmp/installing-wget
+#
+# This will invoke the package manager three times, once for each package,
+# because not all of them are simple package names. You can speed up the
+# process if you have only a few pre-scriots, by using multiple install targets:
+#
+# - install:
+#   - vi
+#   - binutils
+# - install:
+#   - package: wget
+#     pre-script: touch /tmp/installing-wget
+#
+# This will call the package manager once with the package-names "vi" and
+# "binutils", and then a second time for "wget". When installing large numbers
+# of packages, this can lead to a considerable time savings.
+#
+operations:
+  - remove:
+    - app-admin/calamares
+    - app-misc/calamares-sabayon-base-modules
+    - app-misc/calamares-sabayon-branding
+    - app-misc/calamares-sabayon
+    - x11-themes/sabayon-artwork-isolinux
@@ -0,0 +1,2 @@
+---
+username: sabayonlive
@@ -0,0 +1,34 @@
+---
+#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: "cups"
+    mandatory: false
+  - name: "x-setup"
+    mandatory: false
+  - name: "vixie-cron"
+    mandatory: false
+  - name: "oemsystem"
+    mandatory: false
+
+targets:
+  - name: "graphical"
+    mandatory: true
+
+disable:
+  - name: "installer-gui"
+    mandatory: false
+  - name: "installer-text"
+    mandatory: false
+  - name: "sabayonlive"
+    mandatory: false
+  - name: "music"
+    mandatory: false
+  - name: "cdeject"
+    mandatory: false
+
+# Example to express an empty list:
+# disable: []
@@ -0,0 +1,7 @@
+---
+unpack:
+    -   source: "/mnt/cdrom/livecd.squashfs"
+        sourcefs: "squashfs"
+        destination: ""
+
+
@@ -0,0 +1,29 @@
+---
+defaultGroups:
+    - users
+    - lp
+    - video
+    - network
+    - storage
+    - wheel
+    - audio
+    - cdrom
+    - cdrw
+    - usb
+    - plugdev
+    - vboxusers
+    - vboxsf
+    - vboxguest
+    - entropy
+    - portage
+    - messagebus
+    - polkituser
+    - games
+    - scanner
+    - bumblebee
+    - lpadmin
+autologinGroup:  autologin
+doAutologin:     true
+sudoersGroup:    wheel
+setRootPassword: true
+doReusePassword: true
@@ -0,0 +1,150 @@
+# 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:
+#   - modules in $LIBDIR/calamares/moduleswith
+#   - 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.
+#
+# A module that is often used with instances is dummyprocess, which will
+# run a single (shell) command. By configuring more than one instance of
+# the module, multiple shell commands can be run during install.
+#
+# 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.
+#
+# YAML: list of lists of strings.
+sequence:
+- show:
+  - welcome
+#  - dummypythonqt
+  - locale
+  - keyboard
+  - partition
+  - users
+#  - tracking
+  - summary
+- exec:
+#  - dummycpp
+#  - dummyprocess
+#  - dummypython
+#  - dummypythonqt
+  - partition
+  - mount
+  - unpackfs
+  - machineid
+  - fstab
+  - locale
+  - keyboard
+  - localecfg
+  - packages
+#  - luksbootkeyfile
+#  - luksopenswaphookcfg
+#  - dracutlukscfg
+#  - plymouthcfg
+#  - initcpiocfg
+#  - initcpio
+  - users
+  - displaymanager
+  - networkcfg
+  - hwclock
+  - services
+#  - dracut
+  - sabayon
+#  - initramfs
+  - grubcfg
+  - bootloader
+  - umount
+- show:
+#  - webview@owncloud
+  - 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: default
+
+# 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 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. (e.g. partitioning seems like a bad idea, since that is expected to
+# have been done already)
+#
+# Default is false (for a normal installer).
+#
+# YAML: boolean.
+dont-chroot: false
				`@@ -0,0 +1 @@`
				`DIST calamares-sabayon-base-modules-1.11.tar.gz 2791 BLAKE2B bb23609d371dc1e96e75a5d112cdcb476a85cbf2b318000b20ab2f0e07a4d40fa3b26148db70dc0c07d2f7730da31e2c79d580fcdf8caccdf9480e34c83e1ffb SHA512 4b062471e55751ec7be8073c721e1347b88b7a466cd5157429aaa79389062fe08e526bf2e443c262371035134c5d7a8d8366fe8ffbfc00af0b006afc0cde1aae`