How to Install and Uninstall kjournald Package on openSuSE Tumbleweed
Last updated: November 26,2024
1. Install "kjournald" package
Learn how to install kjournald on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
kjournald
Copied
2. Uninstall "kjournald" package
Please follow the guidelines below to uninstall kjournald on openSuSE Tumbleweed:
$
sudo zypper remove
kjournald
Copied
3. Information about the kjournald package on openSuSE Tumbleweed
Information for package kjournald:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : kjournald
Version : 24.02.0-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 494.2 KiB
Installed : No
Status : not installed
Source package : kjournald-24.02.0-1.1.src
Upstream URL : https://invent.kde.org/system/kjournald
Summary : Qt browser for journald database
Description :
This project aims to provide an abstraction of the systemd’s journald API in
terms of QAbstractItemModel classes. The main purpose is to ease the
integration of journald into Qt based applications (both QML and QtWidget).
Additional to the library, the project provides a reference implementation of
the API, called kjournaldbrowser. Even though that application provides a
powerful journal database reader, we aim to do a clear split between
reuseable library and application logic.
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : kjournald
Version : 24.02.0-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 494.2 KiB
Installed : No
Status : not installed
Source package : kjournald-24.02.0-1.1.src
Upstream URL : https://invent.kde.org/system/kjournald
Summary : Qt browser for journald database
Description :
This project aims to provide an abstraction of the systemd’s journald API in
terms of QAbstractItemModel classes. The main purpose is to ease the
integration of journald into Qt based applications (both QML and QtWidget).
Additional to the library, the project provides a reference implementation of
the API, called kjournaldbrowser. Even though that application provides a
powerful journal database reader, we aim to do a clear split between
reuseable library and application logic.