penguins-eggs 10.1.0 → 25.7.7

package/conf/distros/opensuse/calamares/modules/users.yml

@@ -1,19 +1,299 @@
-# Debian/bookworm
+# SPDX-FileCopyrightText: no
+# SPDX-License-Identifier: CC0-1.0
+#
+# Configuration for the one-user-system user module.
+#
+# Besides these settings, the users module also places the following
+# keys into the Global Storage area, based on user input in the view step.
+#
+# - hostname
+# - username
+# - password (obscured)
+# - autologinUser (if enabled, set to username)
+#
+# These Global Storage keys are set when the configuration for this module
+# is read and when they are modified in the UI.
 ---
-userGroup: users
+### GROUPS CONFIGURATION
+#
+# The system has groups of uses. Some special groups must be
+# created during installation. Optionally, there are special
+# groups for users who can use sudo and for supporting autologin.
+
+# Used as default groups for the created user.
+# Adjust to your Distribution defaults.
+#
+# Each entry in the *defaultGroups* list is either:
+#   - a string, naming a group; this is a **non**-system group
+#     which does not need to exist in the target system; if it
+#     does not exist, it will be created.
+#   - an entry with subkeys *name*, *must_exist* and *system*;
+#     if the group *must_exist* and does not, an error is thrown
+#     and the installation fails.
+#
+#     The group is created if it does not exist, and it is
+#     created as a system group (GID < 1000) or user group
+#     (GID >= 1000) depending on the value of *system*.
 defaultGroups:
-  - cdrom
-  - floppy
-  - sudo
-  - audio
-  - dip
-  - video
-  - plugdev
-  - netdev
-  # lpadmin
-  # scanner
-  # bluetooth
-autologinGroup: autologin
-sudoersGroup: sudo
+    - name: users
+      must_exist: true
+      system: true
+    - lp
+    - video
+    - network
+    - storage
+    - name: wheel
+      must_exist: false
+      system: true
+    - audio
+
+# When *sudoersGroup* is set to a non-empty string, Calamares creates a
+# sudoers file for the user. This file is located at:
+#     `/etc/sudoers.d/10-installer`
+# Remember to add the (value of) *sudoersGroup* to *defaultGroups*.
+#
+# If your Distribution already sets up a group of sudoers in its packaging,
+# remove this setting (delete or comment out the line below). Otherwise,
+# the setting will be duplicated in the `/etc/sudoers.d/10-installer` file,
+# potentially confusing users.
+sudoersGroup:    wheel
+
+# Some Distributions require a 'autologin' group for the user.
+# Autologin causes a user to become automatically logged in to
+# the desktop environment on boot.
+# Disable when your Distribution does not require such a group.
+autologinGroup:  autologin
+
+
+### ROOT AND SUDO
+#
+# Some distributions have a root user enabled for login. Others
+# rely entirely on sudo or similar mechanisms to raise privileges.
+
+# If set to `false` (the default), writes a sudoers file with `ALL=(ALL)`
+# so that commands can be run as any user. If set to `true`, writes
+# `ALL=(ALL:ALL)` so that any user and any group can be chosen.
+sudoersConfigureWithGroup: false
+
+# Setting this to false, causes the root account to be disabled.
+# When disabled, hides the "Use the same password for administrator"
+# checkbox. Also hides the "Choose a password" and associated text-inputs.
 setRootPassword: true
-doReusePassword: false
+
+# You can control the initial state for the 'reuse password for root'
+# checkbox here. Possible values are:
+#  - true to check or
+#  - false to uncheck
+#
+# When checked, the user password is used for the root account too.
+#
+# NOTE: *doReusePassword* requires *setRootPassword* to be enabled.
+doReusePassword: true
+
+
+### PASSWORDS AND LOGIN
+#
+# Autologin is convenient for single-user systems, but depends on
+# the location of the machine if it is practical. "Password strength"
+# measures measures might improve security by enforcing hard-to-guess
+# passwords, or might encourage a post-it-under-the-keyboard approach.
+# Distributions are free to steer their users to one kind of password
+# or another. Weak(er) passwords may be allowed, may cause a warning,
+# or may be forbidden entirely.
+
+# Autologin choice can be display to the user.
+# Possible values are:
+#  - true to display it
+#  - false to hide it
+# By default, this value is set to true.
+displayAutologin:   true
+
+# You can control the initial state for the 'autologin checkbox' here.
+# Possible values are:
+#  - true to check or
+#  - false to uncheck
+# These set the **initial** state of the checkbox.
+doAutologin:     true
+
+# These are optional password-requirements that a distro can enforce
+# on the user. The values given in this sample file set only very weak
+# validation settings.
+#
+# Calamares itself supports two checks:
+#   - minLength
+#   - maxLength
+# In this sample file, the values are set to -1 which means "no
+# minimum", "no maximum". This allows any password at all.
+# No effort is done to ensure that the checks are consistent
+# (e.g. specifying a maximum length less than the minimum length
+# will annoy users).
+#
+# Calamares supports password checking through libpwquality.
+# The libpwquality check relies on the (optional) libpwquality library.
+# The value for libpwquality is a list of configuration statements like
+# those found in pwquality.conf. The statements are handed off to the
+# libpwquality parser for evaluation. The check is ignored if
+# libpwquality is not available at build time (generates a warning in
+# the log). The Calamares password check rejects passwords with a
+# score of < 40 with the given libpwquality settings.
+#
+# (additional checks may be implemented in CheckPWQuality.cpp and
+# wired into UsersPage.cpp)
+#
+# To disable all password validations:
+#  - comment out the relevant 'passwordRequirements' keys below,
+#    or set minLength and maxLength to -1.
+#  - disable libpwquality at build-time.
+# To allow all passwords, but provide warnings:
+#  - set both 'allowWeakPasswords' and 'allowWeakPasswordsDefault' to true.
+#    (That will show the box *Allow weak passwords* in the user-
+#    interface, and check it by default).
+#  - configure password-checking however you wish.
+# To require specific password characteristics:
+#  - set 'allowWeakPasswords' to false (the default)
+#  - configure password-checking, e.g. with NIST settings
+
+
+# These are very weak -- actually, none at all -- requirements
+passwordRequirements:
+    minLength: -1  # Password at least this many characters
+    maxLength: -1  # Password at most this many characters
+    libpwquality:
+        - minlen=0
+        - minclass=0
+
+# These are "you must have a password, any password" -- requirements
+#
+# passwordRequirements:
+#     minLength: 1
+
+# These are requirements the try to follow the suggestions from
+#     https://pages.nist.gov/800-63-3/sp800-63b.html , "Digital Identity Guidelines".
+# Note that requiring long and complex passwords has its own cost,
+# because the user has to come up with one at install time.
+# Setting 'allowWeakPasswords' to false and 'doAutologin' to false
+# will require a strong password and prevent (graphical) login
+# without the password. It is likely to be annoying for casual users.
+#
+# passwordRequirements:
+#     minLength: 8
+#     maxLength: 64
+#     libpwquality:
+#         - minlen=8
+#         - maxrepeat=3
+#         - maxsequence=3
+#         - usersubstr=4
+#         - badwords=linux
+
+# You can control the visibility of the 'strong passwords' checkbox here.
+# Possible values are:
+#  - true to show or
+#  - false to hide  (default)
+# the checkbox. This checkbox allows the user to choose to disable
+# password-strength-checks. By default the box is **hidden**, so
+# that you have to pick a password that satisfies the checks.
+allowWeakPasswords: false
+# You can control the initial state for the 'strong passwords' checkbox here.
+# Possible values are:
+#  - true to uncheck or
+#  - false to check (default)
+# the checkbox by default. Since the box is labeled to enforce strong
+# passwords, in order to **allow** weak ones by default, the box needs
+# to be unchecked.
+allowWeakPasswordsDefault: false
+
+
+# User settings
+#
+# The user can enter a username, but there are some other
+# hidden settings for the user which are configurable in Calamares.
+#
+# Key *user* has the following sub-keys:
+#
+# - *shell* Shell to be used for the regular user of the target system.
+#   There are three possible kinds of settings:
+#    - unset (i.e. commented out, the default), act as if set to /bin/bash
+#    - empty (explicit), don't pass shell information to useradd at all
+#      and rely on a correct configuration file in /etc/default/useradd
+#    - set, non-empty, use that path as shell. No validation is done
+#      that the shell actually exists or is executable.
+# - *forbidden_names* Login names that may not be used. This list always
+#   contains "root" and "nobody", but may be extended to list other special
+#   names for a given distro (eg. "video", or "mysql" might not be a valid
+#   end-user login name).
+# - *home_permissions* Home directory of the user is given **approximately**
+#   this set of permissions. If not set, there is no default and no
+#   permission-setting is done (uses defaults of `useradd` in the target).
+#   A umask is computed from these permissions
+#   and passed to `useradd`.
+#
+#   You may write permissions as:
+#   - write "NNN" (three octal digits) or
+#   - write "oNNN" (small 'o' and three octal digits) or
+#   - write "rwxrwxrwx" (like the output of ls, with a - for unset bits)
+#   The following permissions mean the same thing: "o750", "rwxr-x---" .
+user:
+  shell: /bin/bash
+  forbidden_names: [ root ]
+  home_permissions: "o700"
+
+
+# Hostname settings
+#
+# The user can enter a hostname; this is configured into the system
+# in some way. There are settings for how a hostname is guessed (as
+# a default / suggestion) and where (or how) the hostname is set in
+# the target system.
+#
+# Key *hostname* has the following sub-keys:
+#
+# - *location* How the hostname is set in the target system:
+#   - *None*, to not set the hostname at all
+#   - *EtcFile*, to write to `/etc/hostname` directly
+#   - *Etc*, identical to above
+#   - *Hostnamed*, to use systemd hostnamed(1) over DBus
+#   - *Transient*, to remove `/etc/hostname` from the target
+#   The default is *EtcFile*. Setting this to *None* or *Transient* will
+#   hide the hostname field.
+# - *writeHostsFile* Should /etc/hosts be written with a hostname for
+#   this machine (also adds localhost and some ipv6 standard entries).
+#   Defaults to *true*.
+# - *template* Is a simple template for making a suggestion for the
+#   hostname, based on user data. The default is "${first}-${product}".
+#   This is used only if the hostname field is shown. KMacroExpander is
+#   used; write `${key}` where `key` is one of the following:
+#   - *first* User's first name (whatever is first in the User Name field,
+#     which is first-in-order but not necessarily a "first name" as in
+#     "given name" or "name by which you call someone"; beware of western bias)
+#   - *name* All the text in the User Name field.
+#   - *login* The login name (which may be suggested based on User Name)
+#   - *product* The hardware product, based on DMI data
+#   - *product2* The product as described by Qt
+#   - *cpu* CPU name
+#   - *host* Current hostname (which may be a transient hostname)
+#   Literal text in the template is preserved. Calamares tries to map
+#   `${key}` values to something that will fit in a hostname, but does not
+#   apply the same to literal text in the template. Do not use invalid
+#   characters in the literal text, or no suggeston will be done.
+# - *forbidden_names* lists hostnames that may not be used. This list
+#   always contains "localhost", but may list others that are unsuitable
+#   or broken in special ways.
+hostname:
+  location: EtcFile
+  writeHostsFile: true
+  # template: "derp-${cpu}"
+  forbidden_names: [ localhost ]
+
+# Enable Active Directory enrollment support (opt-in)
+#
+# This uses realmd to enroll the machine in an Active Directory server
+# It requires realmd as a runtime dependency of Calamares, if enabled
+allowActiveDirectory: false
+
+presets:
+    fullName:
+        # value: "OEM User"
+        editable: true
+    loginName:
+        # value: "oem"
+        editable: true

package/conf/distros/opensuse/calamares/modules/welcome.yml

@@ -1,19 +1,94 @@
-# Debian/bookworm
-# welcome
+# Configuration for the welcome module. The welcome page
+# displays some information from the branding file.
+# Which parts it displays can be configured through
+# the show* variables.
+#
+# In addition to displaying the welcome page, this module
+# can check requirements for installation.
 ---
-showSupportUrl: true
-showKnownIssuesUrl: true
-showReleaseNotesUrl: true
+# Display settings for various buttons on the welcome page.
+# The URLs themselves come from branding.desc is the setting
+# here is "true". If the setting is false, the button is hidden.
+# The setting can also be a full URL which will then be used
+# instead of the one from the branding file, or empty or not-set
+# which will hide the button.
+showSupportUrl:         true
+showKnownIssuesUrl:     false
+showReleaseNotesUrl:    true
+showDonateUrl:          false
 
+# Requirements checking. These are general, generic, things
+# that are checked. They may not match with the actual requirements
+# imposed by other modules in the system.
 requirements:
-  requiredStorage: 10
-  requiredRam: 1.0
-  check:
-    - storage
-    - ram
-    - power
-    - root
-  required:
-    - storage
-    - ram
-    - root
+    # Amount of available disk, in GiB. Floating-point is allowed here.
+    # Note that this does not account for *usable* disk, so it is possible
+    # to pass this requirement, yet have no space to install to.
+    requiredStorage:    6.0
+
+    # Amount of available RAM, in GiB. Floating-point is allowed here.
+    requiredRam:        1.0
+
+    # To check for internet connectivity, Calamares does a HTTP GET
+    # on this URL; on success (e.g. HTTP code 200) internet is OK.
+    internetCheckUrl:   http://google.com
+
+    # List conditions to check. Each listed condition will be
+    # probed in some way, and yields true or false according to
+    # the host system satisfying the condition.
+    #
+    # This sample file lists all the conditions that are known.
+    check:
+        - storage
+        - ram
+        - power
+        - internet
+        - root
+        - screen
+    # List conditions that **must** be satisfied (from the list
+    # of conditions, above) for installation to proceed.
+    # If any of these conditions are not met, the user cannot
+    # continue past the welcome page.
+    required:
+        # - storage
+        # - ram
+        # - root
+
+# GeoIP checking
+#
+# This can be used to pre-select a language based on the country
+# the user is currently in. It *assumes* that there's internet
+# connectivity, though. Configuration is like in the locale module,
+# but remember to use a URL that returns full data **and** to
+# use a selector that will pick the country, not the timezone.
+#
+# To disable GeoIP checking, either comment-out the entire geoip section,
+# or set the *style* key to an unsupported format (e.g. `none`).
+# Also, note the analogous feature in `src/modules/locale/locale.conf`,
+# which is where you will find complete documentation.
+#
+# For testing, the *style* may be set to `fixed`, any URL that
+# returns data (e.g. `http://example.com`) and then *selector*
+# sets the data that is actually returned (e.g. "DE" to simulate
+# the machine being in Germany).
+#
+# NOTE: the *selector* must pick the country code from the GeoIP
+#       data. Timezone, city, or other data will not be recognized.
+#
+##geoip:
+##    style:    "none"
+##    url:      "https://geoip.kde.org/v1/ubiquity"  # extended XML format
+##    selector: "CountryCode"  # blank uses default, which is wrong
+
+# User interface
+#
+# The "select language" icon is an international standard, but it
+# might not theme very well with your desktop environment.
+# Fill in an icon name (following FreeDesktop standards) to
+# use that named icon instead of the usual one.
+#
+# Leave blank or unset to use the international standard.
+#
+# Known icons in this space are "set-language" and "config-language".
+#
+# languageIcon: set-language

package/conf/distros/opensuse/calamares/settings.yml

@@ -1,124 +1,38 @@
-# Fedora
----
-# "local" is LIBDIR/calamares/modules with settings in SHARE/calamares/modules
-modules-search: [ local, /usr/lib/calamares/modules ]
-
-# If this is set to true, Calamares refers to itself as a "setup program"
-# rather than an "installer". Defaults to the value of dont-chroot, but
-# Calamares will complain if this is not explicitly set.
-oem-setup: false
-
-# If this is set to true, the "Cancel" button will be disabled entirely.
-# The button is also hidden from view.
-#
-# This can be useful if when e.g. Calamares is used as a post-install
-# configuration tool and you require the user to go through all the
-# configuration steps.
-#
-# Default is false, but Calamares will complain if this is not explicitly set.
-#
-# YAML: boolean.
-disable-cancel: false
-
-# If this is set to true, the "Cancel" button will be disabled once
-# you start the 'Installation', meaning there won't be a way to cancel
-# the Installation until it has finished or installation has failed.
-#
-# Default is false, but Calamares will complain if this is not explicitly set.
-#
-# YAML: boolean.
-disable-cancel-during-exec: false
-
-# If this is set to true, then once the end of the sequence has
-# been reached, the quit (done) button is clicked automatically
-# and Calamares will close. Default is false: the user will see
-# that the end of installation has been reached, and that things are ok.
-#
-#
-quit-at-end: false
-
-instances:
-- id:       cleanup
-  module:   shellprocess
-  config:   shellprocess_cleanup.conf
+modules-search: [ local ]
 
 sequence:
-  # Phase 1 - prepare.
-  # View modules are shown as UI pages, jobs from job modules
-  # are executed immediately in the background.
-  # Jobs should be executed sparingly (if at all) in this phase.
-  - show:
-      - welcome
-      - locale
-      - keyboard
-      - partition
-      {{createUsers}}users
-      - summary
-
-  # Phase 2 - install.
-  # View modules are not shown. Only the view modules shown
-  # in the previous phase are allowed, their names should be
-  # added here as placeholders to specify the order in which
-  # view module jobs should be enqueued. Job modules are
-  # also allowed.
-  - exec:
-      - partition
-      - mount
-      - unpackfs
-      {{hasSystemd}}machineid
-      - fstab
-      - locale
-      - keyboard
-      - localecfg
-      - luksbootkeyfile
-      - dracutlukscfg
-      {{createUsers}}users
-      {{hasDisplaymanager}}displaymanager 
-      - networkcfg
-      - hwclock
-      {{hasSystemd}}services-systemd 
-      - dracut
-      - grubcfg
-      - bootloader
-      - packages
-      - removeuser
-      - cleanup
-      - umount
-
-  # Phase 3 - postinstall.
-  # View modules are shown as UI pages, jobs from job modules are
-  # executed immediately in the background.
-  # Jobs should be executed sparingly (if at all) in this phase.
-  - 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.
-# Only the name of the branding component (directory) should be
-# specified here, Calamares then takes care of finding it and
-# loading the contents.
+- show:
+  - welcome
+  - locale
+  - keyboard
+  - partition
+  {{createUsers}}users
+  - summary
+- exec:
+  - partition
+  - mount
+  - unpackfs
+  {{hasSystemd}}machineid
+  - fstab
+  - locale
+  - keyboard
+  - localecfg
+  - plymouthcfg
+  - luksbootkeyfile
+  - dracutlukscfg
+  {{createUsers}}users
+  {{hasDisplaymanager}}displaymanager 
+  - networkcfg
+  - hwclock
+  {{hasSystemd}}services-systemd 
+  - dracut
+  - packages
+  - grubcfg
+  - bootloader
+  - removeuser
+  - umount
+- show:
+  - finished
 branding: {{branding}}
-
-# 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.
+prompt-install: true
 dont-chroot: false

package/conf/distros/opensuse/calamares/zstd2lzo.sh

@@ -0,0 +1,2 @@
+#!/bin/bash
+sed -i 's|\(/ \+btrfs \+defaults,.*\)compress=zstd|\1compress=lzo|g' /etc/fstab

package/conf/distros/rolling/calamares/modules/shellprocess_sync.yml

@@ -0,0 +1,5 @@
+# Arch
+---
+timeout: 5
+script:
+  sync

package/conf/distros/rolling/calamares/settings.yml

@@ -4,9 +4,9 @@
 modules-search: [local, /usr/lib/calamares/modules, /usr/share/calamares]
 
 instances:
-- id:       cleanup
-  module:   shellprocess
-  config:   shellprocess_cleanup.conf
+- id: sync
+  module: shellprocess
+  config: shellprocess_sync.conf
 
 sequence:
   # Phase 1 - prepare.
@@ -40,13 +40,12 @@ sequence:
       {{hasDisplaymanager}}displaymanager 
       - networkcfg
       - hwclock
-      # grubcfg 
+      - shellprocess@sync        # Richiama l'istanza con id: sync
       - bootloader
       - packages
       - luksbootkeyfile
       - plymouthcfg
       - removeuser
-      # shellprocess removelink
       - umount
 
   # Phase 3 - postinstall.

package/dist/classes/bleach.d.ts

@@ -0,0 +1,37 @@
+/**
+ * ./src/classes/bleach.ts
+ * penguins-eggs v.10.0.0 / ecmascript 2020
+ * author: Piero Proietti
+ * email: piero.proietti@gmail.com
+ * license: MIT
+ */
+/**
+ * Bleach:
+ */
+export default class Bleach {
+    /**
+     * clean
+     * @param verbose
+     */
+    clean(verbose?: boolean): Promise<void>;
+    /**
+     *
+     * @param verbose
+     */
+    private cleanFastpack;
+    /**
+     * cleanHistory
+     * @param verbose
+     */
+    private cleanHistory;
+    /**
+     * cleanJournal
+     * @param verbose
+     */
+    private cleanJournal;
+    /**
+     * cleanSystemCache
+     * @param verbose
+     */
+    private cleanSystemCache;
+}