penguins-eggs 25.9.24 → 25.10.3

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

@@ -1,226 +0,0 @@
-# SPDX-FileCopyrightText: no
-# SPDX-License-Identifier: CC0-1.0
-#
-# Configuration file for Calamares
-#
-# This is the top-level configuration file for Calamares.
-# It specifies what modules will be used, as well as some
-# overall characteristics -- is this a setup program, or
-# an installer. More specific configuration is devolved
-# to the branding file (for the UI) and the individual
-# module configuration files (for functionality).
----
-# 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/modules, with
-#   - settings in SHARE/calamares/modules or /etc/calamares/modules.
-# In debug-mode (e.g. calamares -d) "local" also adds some paths
-# that make sense from inside the build-directory, so that you
-# can build-and-run with the latest modules immediately.
-#
-# Strings other than "local" are taken as paths and interpreted
-# relative to wherever Calamares is started. It is therefore **strongly**
-# recommended to use only absolute paths here. This is mostly useful
-# if your distro has forks of standard Calamares modules, but also
-# uses some form of upstream packaging which might overwrite those
-# forked modules -- then you can keep modules somewhere outside of
-# the "regular" module tree.
-#
-#
-# 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 these keys:
-# - *module* name, which matches the module name from the module descriptor
-#   (usually the name of the directory under `src/modules/`, but third-
-#   party modules may diverge.
-# - *id* (optional) an identifier to distinguish this instance from
-#   all the others. If none is given, the name of the module is used.
-#   Together, the module and id form an instance key (see below).
-# - *config* (optional) a filename for the configuration. If none is
-#   given, *module*`.conf` is used (e.g. `welcome.conf` for the welcome
-#   module)
-# - *weight* (optional) In the *exec* phase of the sequence, progress
-#   is reported as jobs are completed. The jobs from a single module
-#   together contribute the full weight of that module. The overall
-#   progress (0 .. 100%) is divided up according to the weight of each
-#   module. Give modules that take a lot of time to complete, a larger
-#   weight to keep the overall progress moving along steadily. This
-#   weight overrides a weight given in the module descriptor. If no weight
-#   is given, uses the value from the module descriptor, or 1 if there
-#   isn't one there either.
-#
-# 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.
-# "packagechooserq@licenseq", where "packagechooserq" is the module name (for the packagechooserq
-# viewmodule) and "licenseq" is the instance name. In the *sequence*
-# section below, use instance-keys to name instances (instead of just
-# a module name, for modules which have only a single instance).
-#
-# Every module implicitly has an instance with the instance name equal
-# to its module name, e.g. "welcome@welcome". In the *sequence* section,
-# mentioning a module without a full instance key (e.g. "welcome")
-# means that implicit module.
-#
-# An instance may specify its configuration file (e.g. `webview-home.conf`).
-# The implicit instances all have configuration files named `<module>.conf`.
-# This (implict) way matches the source examples, where the welcome
-# module contains an example `welcome.conf`. Specify a *config* for
-# any module (also implicit instances) to change which file is used.
-#
-# 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 shellprocess, which will
-# run shell commands specified in the configuration file. By configuring
-# more than one instance of the module, multiple shell sessions can be run
-# during install.
-#
-# YAML: list of maps of string:string key-value pairs.
-#instances:
-#- id:       licenseq
-#  module:   packagechooserq
-#  config:   licenseq.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
-  - locale
-  - keyboard
-  - partition
-  - users
-  - summary
-- exec:
-  - partition
-  - mount
-  - unpackfs
-  - machineid
-  - fstab
-  - locale
-  - keyboard
-  - localecfg
-  - luksbootkeyfile
-  - luksopenswaphookcfg
-  - dracutlukscfg
-  - plymouthcfg
-  - users
-  - displaymanager 
-  - networkcfg
-  - hwclock
-  - services-systemd
-  - dracut
-  - packages
-  - 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: 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, but Calamares will complain if
-# this is not explicitly set.
-#
-# YAML: boolean.
-prompt-install: true
-
-# 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), but Calamares will complain if
-# this is not explicitly set.
-#
-# YAML: boolean.
-dont-chroot: false
-
-# 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, the "Next" and "Back" button will be hidden once
-# you start the 'Installation'.
-#
-# Default is false, but Calamares will complain if this is not explicitly set.
-#
-# YAML: boolean.
-hide-back-and-next-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

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

@@ -1,6 +0,0 @@
-# Arch
-# Calamares 3.3
----
-backend: pacman
-
-{{operations}}

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

@@ -1,75 +0,0 @@
-# arch
-# calamares 3.3
----
-# A variable from global storage which overrides the value of efiBootLoader
-#efiBootLoaderVar: "packagechooser_bootloader"
-
-# Define which bootloader you want to use for EFI installations
-# Possible options are 'grub', 'sb-shim', 'refind` and 'systemd-boot'.
-efiBootLoader: "grub"
-
-# systemd-boot configuration files settings
-
-# kernelSearchPath is the path relative to the root of the install to search for kernels
-# A kernel is identified by finding files which match regular expression, kernelPattern
-kernelSearchPath: "/usr/lib/modules"
-kernelPattern: "^vmlinuz.*"
-
-# loaderEntries is an array of options to add to loader.conf for systemd-boot
-# please note that the "default" option is added programmatically
-loaderEntries:
-  - "timeout 5"
-  - "console-mode keep"
-
-# systemd-boot and refind support custom kernel params
-kernelParams: [ "quiet" ]
-
-# A list of kernel names that refind should accept as kernels
-#refindKernelList: [ "linux","linux-lts","linux-zen","linux-hardened" ]
-
-# GRUB 2 binary names and boot directory
-# Some distributions (e.g. Fedora) use grub2-* (resp. /boot/grub2/) names.
-# These names are also used when using sb-shim, since that needs some
-# GRUB functionality (notably grub-probe) to work. As needed, you may use
-# complete paths like `/usr/bin/efibootmgr` for the executables.
-#
-grubInstall: "grub-install"
-grubMkconfig: "grub-mkconfig"
-grubCfg: "/boot/grub/grub.cfg"
-grubProbe: "grub-probe"
-efiBootMgr: "efibootmgr"
-
-# Optionally set the bootloader ID to use for EFI. This is passed to
-# grub-install --bootloader-id.
-#
-# If not set here, the value from bootloaderEntryName from branding.desc
-# is used, with problematic characters (space and slash) replaced.
-#
-# The ID is also used as a directory name within the EFI environment,
-# and the bootloader is copied from /boot/efi/EFI/<dirname>/ . When
-# setting the option here, keep in mind that the name is sanitized
-# (problematic characters, see above, are replaced).
-#
-# There are some special words possible at the end of *efiBootloaderId*:
-#   ${SERIAL} can be used to obtain a uniquely-numbered suffix
-#       that is added to the Id (yielding, e.g., `dirname1` or `dirname72`)
-#   ${RANDOM} can be used to obtain a unique 4-digit hex suffix
-#   ${PHRASE} can be used to obtain a unique 1-to-3-word suffix
-#       from a dictionary of space-themed words
-# These words must be at the **end** of the *efiBootloaderId* value.
-# There must also be at most one of them. If there is none, no suffix-
-# processing is done and the *efiBootloaderId* is used unchanged.
-#
-# NOTE: Debian derivatives that use the unmodified Debian GRUB EFI
-#       packages may need to set this to "debian" because that is
-#       hard-coded in `grubx64.efi`.
-#
-# efiBootloaderId: "dirname"
-
-# Optionally install a copy of the GRUB EFI bootloader as the EFI
-# fallback loader (either bootia32.efi or bootx64.efi depending on
-# the system). This may be needed on certain systems (Intel DH87MC
-# seems to be the only one). If you set this to false, take care
-# to add another module to optionally install the fallback on those
-# boards that need it.
-installEFIFallback: true

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

@@ -1,21 +0,0 @@
-# Arch
-# calamares-33
----
-#The DM module attempts to set up all the DMs found in this list, in that precise order.
-#It also sets up autologin, if the feature is enabled in globalstorage.
-#The displaymanagers list can also be set in globalstorage, and in that case it overrides anything set up here.
-displaymanagers: none
-
-#Enable the following settings to force a desktop environment in your displaymanager configuration file:
-#defaultDesktopEnvironment:
-#    executable: "startkde"
-#    desktopFile: "plasma"
-
-#If true, try to ensure that the user, group, /var directory etc. for the
-#display manager are set up correctly. This is normally done by the distribution
-#packages, and best left to them. Therefore, it is disabled by default.
-basicSetup: false
-
-#If true, setup autologin for openSUSE. This only makes sense on openSUSE
-#derivatives or other systems where /etc/sysconfig/displaymanager exists.
-sysconfigSetup: false

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

@@ -1,47 +0,0 @@
-# Arch
-# Calamares 3.3
----
-# DEPRECATED
-#
-# The finished page can hold a "restart system now" checkbox.
-# If this is false, no checkbox is shown and the system is not restarted
-# when Calamares exits.
-# restartNowEnabled: true
-
-# DEPRECATED
-#
-# Initial state of the checkbox "restart now". Only relevant when the
-# checkbox is shown by restartNowEnabled.
-# restartNowChecked: false
-
-# Behavior of the "restart system now" button.
-#
-# There are four usable values:
-#   - never
-#       Does not show the button and does not restart.
-#       This matches the old behavior with restartNowEnabled=false.
-#   - user-unchecked
-#       Shows the button, defaults to unchecked, restarts if it is checked.
-#       This matches the old behavior with restartNowEnabled=true and restartNowChecked=false.
-#   - user-checked
-#       Shows the button, defaults to checked, restarts if it is checked.
-#       This matches the old behavior with restartNowEnabled=true and restartNowChecked=true.
-#   - always
-#       Shows the button, checked, but the user cannot change it.
-#       This is new behavior.
-#
-# The three combinations of legacy values are still supported.
-#restartNowMode: user-unchecked 
-restartNowEnabled: true
-restartNowChecked: true
-# If the checkbox is shown, and the checkbox is checked, then when
-# Calamares exits from the finished-page it will run this command.
-# If not set, falls back to "shutdown -r now".
-restartNowCommand: none
-
-# When the last page is (successfully) reached, send a DBus notification
-# to the desktop that the installation is done. This works only if the
-# user as whom Calamares is run, can reach the regular desktop session bus.
-notifyOnFinished: false
-
-

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

@@ -1,31 +0,0 @@
-# Arch
-# calamares 3.3
----
-
-# Additional options added to each line in /etc/crypttab
-crypttabOptions: luks
-# For Debian and Debian-based distributions, change the above line to:
-# crypttabOptions: luks,keyscript=/bin/cat
-
-# Options for handling /tmp in /etc/fstab
-# Currently default (required) and ssd are supported
-# The corresponding string can contain the following variables:
-# tmpfs: true or tmpfs: false to either mount /tmp as tmpfs or not
-# options: "<mount options>"
-#
-# Example:
-#tmpOptions:
-#    default:
-#        tmpfs: false
-#        options: ""
-#    ssd:
-#        tmpfs: true
-#        options: "defaults,noatime,mode=1777"
-#
-tmpOptions:
-    default:
-        tmpfs: false
-        options: ""
-    ssd:
-        tmpfs: true
-        options: "defaults,noatime,mode=1777"

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

@@ -1,5 +0,0 @@
-# Arch
-# Calamares 3.3
----
-# Path of the configuration file to write (in the target system)
-configFilePath: /etc/openswap.conf

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

@@ -1,40 +0,0 @@
-# Arch
-# Calamares 3.3
----
-# Whether to create /etc/machine-id for systemd.
-# The default is *false*.
-systemd: true
-
-# Whether to create /var/lib/dbus/machine-id for D-Bus.
-# The default is *false*.
-dbus: true
-# Whether /var/lib/dbus/machine-id should be a symlink to /etc/machine-id
-# (ignored if dbus is false, or if there is no /etc/machine-id to point to).
-# The default is *false*.
-dbus-symlink: true
-
-# Copy entropy from the host? If this is set to *true*, then
-# any entropy file listed below will be copied from the host
-# if it exists. Non-existent files will be generated from
-# /dev/urandom . The default is *false*.
-entropy-copy: false
-# Which files to write (paths in the target). Each of these files is
-# either generated from /dev/urandom or copied from the host, depending
-# on the setting for *entropy-copy*, above.
-entropy-files:
-    - /var/lib/urandom/random-seed
-    - /var/lib/systemd/random-seed
-
-# Whether to create an entropy file /var/lib/urandom/random-seed
-#
-# DEPRECATED: list the file in entropy-files instead. If this key
-# exists and is set to *true*, a warning is printed and Calamares
-# behaves as if `/var/lib/urandom/random-seed` is listed in *entropy-files*.
-#
-# entropy: false
-
-# Whether to create a symlink for D-Bus
-#
-# DEPRECATED: set *dbus-symlink* with the same meaning instead.
-#
-# symlink: false

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

@@ -1,115 +0,0 @@
-# Arch
-# calamares 3.3
----
-# Extra filesystems to mount. The key's value is a list of entries; each
-# entry has five keys:
-#   - device    The device node to mount
-#   - fs (optional) The filesystem type to use
-#   - mountPoint Where to mount the filesystem
-#   - options (optional) An array of options to pass to mount
-#   - efi (optional) A boolean that when true is only mounted for UEFI installs
-#
-# The device is not mounted if the mountPoint is unset or if the fs is
-# set to unformatted.
-#
-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 ]
-    - device: efivarfs
-      fs: efivarfs
-      mountPoint: /sys/firmware/efi/efivars
-      efi: true
-
-# Btrfs subvolumes to create if root filesystem is on btrfs volume.
-# If *mountpoint* is mounted already to another partition, it is ignored.
-# Separate subvolume for swapfile is handled separately and automatically.
-#
-# It is possible to prevent subvolume creation -- this is likely only relevant
-# for the root (/) subvolume -- by giving an empty string as a subvolume
-# name. In this case no subvolume will be created.
-#
-btrfsSubvolumes:
-    - mountPoint: /
-      subvolume: /@
-      # As an alternative:
-      #
-      # subvolume: ""
-    - mountPoint: /home
-      subvolume: /@home
-    - mountPoint: /var/cache
-      subvolume: /@cache
-    - mountPoint: /var/log
-      subvolume: /@log
-
-# The name of the btrfs subvolume holding the swapfile.  This only used when
-# a swapfile is selected and the root filesystem is btrfs
-#
-btrfsSwapSubvol: /@swap
-
-# The mount options used to mount each filesystem.
-#
-# filesystem contains the name of the filesystem or on of three special
-# values, "default", efi" and "btrfs_swap".  The logic is applied in this manner:
-#   - If the partition is the EFI partition, the "efi" entry will be used
-#   - If the fs is btrfs and the subvolume is for the swapfile,
-#     the "btrfs_swap" entry is used
-#   - If the  filesystem is an exact match for filesystem, that entry is used
-#   - If no match is found in the above, the default entry is used
-#   - If there is no match and no default entry, "defaults" is used
-#   - If the mountOptions key is not present, "defaults" is used
-#
-# Each filesystem entry contains 3 keys, all of which are optional
-#   options - An array of mount options that is used on all disk types
-#   ssdOptions - An array of mount options combined with options for ssds
-#   hddOptions - An array of mount options combined with options for hdds
-# If combining these options results in an empty array, "defaults" is used
-#
-# Example 1
-# In this example, there are specific options for ext4 and btrfs filesystems,
-# the EFI partition and the subvolume holding the btrfs swapfile.  All other
-# filesystems use the default entry.  For the btrfs filesystem, there are
-# additional options specific to hdds and ssds
-#
-# mountOptions:
-#    - filesystem: default
-#      options: [ defaults ]
-#    - filesystem: efi
-#      options: [ defaults, umask=0077 ]
-#    - filesystem: ext4
-#      options: [ defaults, noatime ]
-#    - filesystem: btrfs
-#      options: [ defaults, noatime, compress=zstd:1 ]
-#      ssdOptions: [ discard=async ]
-#      hddOptions: [ autodefrag ]
-#    - filesystem: btrfs_swap
-#      options: [ defaults, noatime ]
-#
-# Example 2
-# In this example there is a single default used by all filesystems
-#
-# mountOptions:
-#    - filesystem: default
-#      options: [ defaults, noatime ]
-#
-mountOptions:
-    - filesystem: default
-      options: [ defaults, noatime ]
-    - filesystem: efi
-      options: [ defaults, umask=0077 ]
-    - filesystem: btrfs
-      options: [ defaults, noatime, compress=lzo ]
-    - filesystem: btrfs_swap
-      options: [ defaults, noatime ]

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

@@ -1,6 +0,0 @@
-# Arch
-# Calamares 3.3
----
-backend: pacman
-
-{{operations}}

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

@@ -1,16 +0,0 @@
-# Arch
-# Calamares 3.3
-#
-# SPDX-FileCopyrightText: no
-# SPDX-License-Identifier: CC0-1.0
-#
-# Removes a single user (with userdel) from the system.
-# This is typically used in OEM setups or if the live user
-# spills into the target system.
-#
-# The module never fails; if userdel fails, this is logged
-# but the module still reports success and installation / setup
-# continues as normal.
----
-# Username in the target system to be removed.
-username: {{username}}

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

@@ -1,7 +0,0 @@
-# Arch 
-# calamares-3.3
----
-unpack:
-    -   source: {{source}}
-        sourcefs: "squashfs"
-        destination: ""

package/conf/distros/stretch/README.md

@@ -1,4 +0,0 @@
-# Debian 9 stretch
-
-It take all configuration of Debian buster
-it use krill

package/conf/distros/stretch/krill/krill-modules/bootloader-config/bootloader-config.sh

@@ -1,28 +0,0 @@
-#!/bin/bash
-
-CHROOT=$(mount | grep proc | grep krill | awk '{print $3}' | sed -e "s#/proc##g")
-
-# Creo la directory $CHROOT/tmp se mancante 
-TMPDIR=$CHROOT/tmp
-if [ ! -d $TMPDIR ]; then
-    echo mkdir $TMPDIR
-fi
-# eseguo apt update
-chroot $CHROOT apt-get -y --allow-unauthenticated update
-# Set secure permissions for the initramfs if we're configuring
-# full-disk-encryption. The initramfs is re-generated later in the
-# installation process so we only set the permissions snippet without
-# regenerating the initramfs right now:
-if [ "$(mount | grep $CHROOT" " | cut -c -16)" = "/dev/mapper/luks" ]; then
-    echo "UMASK=0077" > $CHROOT/etc/initramfs-tools/conf.d/initramfs-permissions
-fi
-
-echo "Running bootloader-config..."
-
-if [ -d /sys/firmware/efi/efivars ]; then
-    echo " * Installing grub-efi (uefi)..."
-    DEBIAN_FRONTEND=nointeractive chroot $CHROOT apt-get -y --allow-unauthenticated install grub-efi-amd64 cryptsetup keyutils
-else
-    echo " * install grub... (bios)"
-    DEBIAN_FRONTEND=nointeractive chroot $CHROOT apt-get -y --allow-unauthenticated install grub-pc cryptsetup
-fi

package/conf/distros/stretch/krill/krill-modules/remove-link/module.yml

@@ -1,9 +0,0 @@
-# Debian Buster
-# remove-link
----
-type: "job"
-name: "remove-link"
-interface: "process"
-chroot: false
-command: "/usr/sbin/remove-link.sh"
-timeout: 8

package/conf/distros/stretch/krill/krill-modules/remove-link/remove-link.sh

@@ -1,5 +0,0 @@
-#!/bin/bash
-CHROOT=$(mount | grep proc | grep krill | awk '{print $3}' | sed -e "s#/proc##g")
-rm $CHROOT/usr/share/applications/install-system.desktop
-rm $CHROOT/usr/share/applications/penguins-krill.desktop
-rm $CHROOT/usr/share/applications/penguins-clinstaller.desktop