These come from the `stoken` package, which got pulled in as a
dependency of `openconnect` in e7aa97f0fd.
We don't want these GUI apps cluttering up the menu structure; their
icons are ugly, and when you launch them, they just show an
incomprehensible error message and quit.
it shouldn't be necessary any longer since we now generate all locales
into the image itself. in fact the mount is getting in the way of those
generated locales working
We don't want people finding and using it anyway, and it isn't
even functional because we don't include a /etc/pacman.conf file. It
was only ever intended to be here for local debugging during bring-up,
but the fact thst it hasn't worked shows that this isn't very important
either. Let's delete it.
Fixes#161
unfortunately the tmpfiles.d/40-etc.conf ran in addition to
tmpfiles.d/etc.conf (from systemd) and the latter copies systemd's pam.d
configs out of /usr/share/factory into /etc. those configs then break
pam by overriding our actual configs in /usr/lib/pam.d
fixing this is a bit tricky. to fix new systems we simply overwrite the
etc.conf from systemd and as an additional safeguard remove etc/pam.d
from the factory directory.
to fix existing installations a new service is being added that runs a
simple cleanup program. as part of reaching the basic.target
Fixes#165
requires kde-linux.erofs=1 to opt in.
expects a kde-linux.erofs in the root of the root partition.
the biggest change here is a new mount generator that replaces the old
overlay tech. to assit in migration a transition script is invoked as
part of the mount actions. all of this happens in the initrd.
after switch into the real root the most important part is the tmpfiles
system which should make sure to populate etc on clean installations
assuming the prototype works out this would render /usr readonly while
the rest of the system can just be a plain old btrfs
this introduces a new cmdline arg `kde-linux.erofs=1` which enables
erofs mode. currently this does nothing besides disabling the overlay.
in the future this will be a testing toggle for an erofs based system
Ensure that the default shell has a proper editor set by defining EDITOR as vim. This prevents issues where Git cannot open an editor when committing changes.
Solves #163
Fix issue #140: Transition KDE apps to nightly Flatpak versions
Updated the download_flatpaks function to install KDE apps from the KDE nightly Flatpak repository instead of Flathub. This ensures that the bundled KDE apps are pulled from the nightly builds, reflecting the latest development versions of the software.
The following changes were made:
- Added the KDE nightly repository to the Flatpak configuration.
- Updated the installation of KDE apps to use nightly builds (ark, dolphin, elisa, gwenview, kate, haruna, konsole, kwrite, okular).
- Kept Mozilla Firefox installation from Flathub for stable releases.
This update addresses issue #140, ensuring that the Testing edition uses nightly versions of bundled KDE apps.
the one in the docker image has been made to not extract localization
tech as of late. seeing as we need (some) localization data to generate
locales and whatnot we need to restore the original config
This reverts commit efa56847ed.
as it turns out we do need the archives after all. as per glibc
documentation the two operation modes are either one large archive or
multiple small archives. there seems to be no way to run without archive
(indeed, it seems fair to spend a bit more time generating the image
instead of paying for locales at every app startup)
- remove overbaring debugging
- don't print exceptions or handle exceptions when they are meant to be
fatal
- don't open the file multiple times
- don't check uid, it's inconsequental because we really only need a
writable file
Amends 6341baed9d.
It's broken due to Konsole being in a Flatpak, which suffers from Bug
495551. Even if it were working, this is kind of useless since it just
launches the CLI command anyway. Let's remove it.
nvtop is basically the GPU companion to htop, which we do already
include.
ydotool is useful for basic automation, which enthusiasts and developers
often benefit from.
Relevant to #12
We currently include the firewall KCM but no firewall! Instead of
getting rid of the KCM, let's add a firewall. Ufw is sane enough, at
least until the KCM supports zones which is necessary to fully support
the competing firewalld firewall.
Resolves#112
This reverts commit b294a76309.
The template system was put in place to differentiate what is in the live
image and what needs to be in the target system. doing away with it
broke the installation
In the past this has been requested as a Flatpak, but I believe that it
fits better as a pre-installed package because it's system enablement
for touch devices; without it, they simply don't work. As such, the user
shouldn't be able to remove it or swap it out for something else
(because it's the only thing we support right now anyway).
It isn't suitable for our use case since it's more than just an app; it
provides a KCM as well. This doesn't (and can't) come through in the
Flatpak packaging of it, so we're missing the KCM in System Settings,
and that's a problem.
Instead, let's let the software be built from source using kde-builder.
Depends on
https://invent.kde.org/kde-linux/kde-linux-packages/-/merge_requests/15
