AKABEI.CONF(5)

NAME
akabei.conf - Chakra package manager: configuration file

SYNOPSIS

/etc/akabei.conf

DESCRIPTION

Akabei will try to read configuration settings from this file at every invocation. The configuration file is divided into sections (also referred to as groups) plus special sections specifying repositories. For each group there is a set of options the user can set inside the group. Sections are started with a special line containing only [section name] (see the example below).

The configuration file can be modified manually, or automatically using the akabei-config(8) tool, or generated from a pacman.conf file using akabei-conf-import(8).

Quick note: most of the options explained below can be specified from the command line too. The command line always overrides whatever it’s written in the configuration file, but of course the new setting is valid only during the current akabei execution.

GENERAL SECTION

This section contains most of the Akabei options. Note: list elements must be separated with one blank space.

RootDir = <path>
    Set the default root directory akabei will run into. It is a required option.

DatabaseDir = <path>
    Overrides the default location akabei will look for its databases in. It is a required option: in most cases, you can keep it to the default value.

CacheDir = <path>
    Overrides the default location of the cache directory. It is a required option.

LogFile = <file path>
    Sets a different path for the log file. A typical default is /var/log/akabei.log.

UseSyslog = <yes|no>
    Instructs akabei to use the system logger to log information. Logs can be then displayed using dmesg(1). Default: no.

NoUpgrade = <file list>
    All files listed here will never be touched (i.e. replaced) during an install/upgrade; the new files will be saved with an .akabeinew extension. The filenames refer to files inside package archives, so don’t include the leading slash (the root directory) in their path.

NoExtract = <file list>
    All files listed here will never be extracted from a package into the filesystem. This is useful when you don’t want to install all the files belonging to a certain package. The filenames refer to files inside package archives, so don’t include the leading slash (the root directory) in their path.

HoldPkg = <package list>
    If a package in this list is to be removed from the system, akabei will first ask for confirmation to the user.

SyncFirst = <package list>
    When upgrading the system, if a newer version of a package in this list is found, the user will be asked to update this one first: the choice is to either cancel the current operation to update the package and restart it later, or going on with the operation. It is important you keep at least akabei in this list (it’s there by default): if akabei has to be updated, we strongly suggest not to perform operations using the old version, risking inconsistencies in the package manager.

IgnorePkg = <package list>
    Instructs akabei to ignore every upgrade for packages in this list.

IgnoreGroup = <group list>
    Instructs akabei to ignore every upgrade for packages in at least one group of the list.

CACHE SECTION

KeepPackages = <package list>
    Packages in this list are never removed from the cache.

MaxSize = <x>
    If this option is specified, the cache cannot occupy more than x megabytes. See below for what happens when the cache exceeds this size.

MaxSizePolicy = <CleanAll|CleanOld|CleanUnused>
    Specifies the action to be performed when the cache exceeds the maximum size allowed.

        • CleanAll: all the packages are removed.

        • CleanOld: cleans only the oldest, i.e. those in cache for more than 2 weeks.

        • CleanUnused: clean only the least used, i.e. those not accessed by akabei for more than 2 weeks.

        If the user chooses CleanOld or CleanUnused, the cache size will be (at most) halved. CleanAll is the default behavior if the user sets a maximum size.

REPOSITORY SECTION(S)

Each section here identifies a valid repository for akabei: a repository is defined by a name and at least one location where packages can be downloaded. Locations are defined by the Server directive, associated to an URL (remote or local as well), or by an Include directive, associated to the path to a file which must contain a list of server URLs.

EXAMPLE

    #
    # akabei.conf
    #
    [General]
    RootDir=/
    CacheDir=/var/cache/akabei
    DatabaseDir=/var/lib/akabei
    SyncFirst=akabei
    HoldPkg=akabei glibc
    [cache]
    MaxSize=30
    [core]
    Server = https://rsync.chakralinux.org/packages/core/x86_64
    [testing]
    Include=/etc/akabei/mirrorlist

BUGS

Report any bug in the official Chakra BugTracker, https://code.chakralinux.org in the Akabei section. Try to include as much detail as possible in your explanation.

SEE ALSO

akabei(8), akabei-config(8), akabei-conf-import(8)

AUTHOR

Lisa Vitolo <<shainer@chakralinux.org>>
    Author.