A glossary of common terms.
A storage service for personal information management (PIM) data and metadata.
A metadata and search framework by KDE. Replaces Nepomuk since KDE SC 4.13.
The bugtracker is a web application where users can (and should) report outdated packages, broken packages, requests features to be added and of course report bugs and other issues found on the website or in other projects developed by the Chakra developers or packagers.
An operating system and a GNU/Linux distribution. Chakra should be referred to as:
- chakra (UNIX name)
Chakra Linux is also acceptable although GNU/Linux and KDE/Qt is implied. On social networks the "hashtag" #chakralinux is used to make a distinction between a religious topic and a technical (operating system) one. "ChakraLinux", "Chakralinux", "chakralinux", "cHaKrAlInUx", etc. are all weird and weirder mutations.
GnuPG, GNU Privacy Guard, a complete and free implementation of the OpenPGP standard as defined by RFC4880 (also known as PGP). GnuPG allows to encrypt and sign your data and communication, features a versatile key management system as well as access modules for all kinds of public key directories.
Internet Relay Chat is a protocol that facilitates communication in the form of text. The chat process works on a client/server networking model. IRC clients are computer programs that a user can install on their system. These clients communicate with chat servers to transfer messages to other clients. IRC is mainly designed for group communication in discussion forums, called channels, but also allows one-on-one communication via private messages and more.
KConfig Module. KCMs can help you configure your system by providing interfaces in System Settings, or through the command line with kcmshell5.
An international free software community producing an integrated set of cross-platform applications designed to run on modern Unix-like and Microsoft Windows systems. It is known for Plasma, a desktop environment.
KWin is the default window manager in Chakra.
The kernel used in Chakra.
A live media or live disc is a complete bootable computer installation including Chakra which runs in a computer's memory, rather than loading from a hard disk drive; the media itself is read-only. It allows users to run Chakra for any purpose without installing it or making any changes to the computer's configuration. Live media can run on a computer without secondary storage, such as a hard disk drive, or with a corrupted hard disk drive or file system, allowing data recovery. Chakra releases have names of the form "chakra-YYYY.MM-CODENAME-ARCHITECTURE.iso" and can be found at rsync.chakralinux.org/releases/.
makepkg will build packages for you. makepkg will read the metadata required from a PKGBUILD file. All it needs is a build-capable Linux platform, wget, and some build scripts. The advantage to a script-based build is that you only really do the work once. Once you have the build script for a package, you just need to run makepkg and it will do the rest: download and validate source files, check dependencies, configure the build time settings, build the package, install the package into a temporary root, make customizations, generate meta-info, and package the whole thing up for pacman to use.
A third-party server that copies the package repositories on rsync.chakralinux.org to itself, that users may select to download from a location closer to themselves and reducing the bandwidth usage for Chakra.
"Networked Environment for Personalized, Ontology-based Management of Unified Knowledge", Nepomuk aims to remove artificial barriers between information to allow dynamic classification, organisation and presentation of data to the user. Whether downloaded from the internet, received in an email or scribbled in a note, information is globally searchable and tagged with intelligent data. Replaced by Baloo in KDE SC 4.13.
A package (sometimes referred to as "binary package" do distinguish it from source packages) is an archive containing
- all of the (compiled) files of an application
- metadata about the application, such as application name, version, dependencies, ...
- installation files and directives for pacman
- (optionally) extra files to make your life easier, such as a start/stop script
- easily updatable: pacman will update existing packages as soon as updates are available
- dependency checks: pacman handles dependencies for you, you only need to specify the program and pacman installs it together with every other program it needs
- clean removal: pacman has a list of every file in a package. This way, no files are left behind when you decide to remove a package.
A contributor who packages software for Chakra. The role of the packager (or "package maintainer", which is in relation to a specific package) is to update packages as new versions become available upstream and to field support questions relating to bugs in said packages. While usually used to denote those contributors who are officially recognized and listd as contributors to Chakra (i.e. junior and senior packagers) the term may be applied to any of the following:
- A senior packager, abbreviated as Sr. Packager, who maintains one or more software packages in [core].
- A junior packager, abbreviated as Jr. Packager, who maintains one or more software packages in [desktop], [gtk] or [lib32].
- A CCR Trusted User of the community who maintains software packages in the CCR.
- A CCR Packager, essentially a normal user, who maintains a source package in the CCR.
The maintainer of a package is the person currently responsible for the package. Previous maintainers should be listed as contributors in the PKGBUILD along with others who have contributed to the package.
The pacman package manager is one of the great highlights of Chakra. It combines a simple binary package format with an easy-to-use build system (see CBS). Pacman makes it possible to easily manage and customize packages, whether they be from the official Chakra repositories or the user's own creations. The repository system allows users to build and maintain their own custom package repositories, which encourages community growth and contribution (also see CCR).
Pacman can keep a system up to date by synchronizing package lists with the master server, making it a breeze for the security-conscious system administrator to maintain. This server/client model also allows you to download/install packages with a simple command, complete with all required dependencies (similar to Debian's apt-get).
NB: Pacman was written by Judd Vinet, the creator of Arch Linux.
This is the configuration file of pacman. It is located at /etc/pacman.conf. For a full explanation, run this in Konsole or a TTY:
This is the log file of pacman. It is located in /var/log/pacman.log. It is useful when troubleshooting to find out if something went wrong during an upgrade.
Pretty Good Privacy (PGP) is a data encryption and decryption computer program that provides cryptographic privacy and authentication for data communication. PGP is often used for signing, encrypting, and decrypting texts, e-mails, files, directories, and whole disk partitions and to increase the security of e-mail communications.
PKGBUILDs are small scripts that are used to build packages.
Plasma, or Plasma Desktop, or KDE Plasma 4, or KDE Plasma 5 - the default desktop environment in Chakra. Usually simply referred to as Plasma. KDE Plasma Workspaces is or was the umbrella term for the fourth generation graphical environments developed by KDE.
A repository contains packages that are built and ready to be installed. The official repositories are
Pacman uses these repositories to search for packages and install them. A repository can be local (i.e. on your own computer) or remote (i.e. the packages are downloaded before they are installed). Anyone can create a repository and put it online for other users. To create a repository, you need a set of packages and a pacman-compatible database file for your packages. Host your files online and everyone will be able to use your repository by adding it as a regular repository.
Software in the Public Interest, a non-profit organization which was founded to help organizations develop and distribute open hardware and software. Chakra is a member, and relies upon SPI to accept donations and hold property.
A deep-indexed search daemon, Strigi aims to be fast and light-weight. It also uses SHA-1 hash which will help in the identification of duplicate files.
The GNU version of the tar archiving utility, an archiving program designed to store and extract files from an archive file known as a tarfile or tarball.
TTY stands for teletype, but has come to mean any type of text terminal. You can switch to TTY one through eight by holding down the Control and Alt keys on your keyboard followed by pressing any of the first eight function keys (F1, F2 etc.). The X window system will usually be running on the seventh. Also see Konsole.
A general-purpose data compression tool.
The [core] repository contains the bare essentials needed for a Chakra system - everything that is necessary to get Plasma running. Most notably this includes the Linux kernel, drivers and Plasma itself with its dependencies.
Extra, non-essential software.
Notable and popular software depending on the GTK toolkit as well as GTK libraries.
Allows the user to run and build 32-bit applications on installations of Chakra (which are 64-bit). [lib32] creates a directory containing 32-bit instruction set libraries inside /usr/lib32/, which 32-bit binary applications may need when executed.
Temporary holding area for packages, while a group of packages is being prepared, before they are moved to another repository. Not intended for users to fetch packages from - doing so may break your system.
This is the repository where updates to packages are kept prior to being moved into the stable repositories: [core], [desktop], [lib32] and [gtk]. This allows for them to be tested and that potential issues can be found. It is disabled by default but can be enabled in pacman.conf.
Development versions of software.
|Frequently Asked Questions|
These are questions about Chakra that are often expressed in the forum, IRC and conversations with reviewers.