Repositories¶
Obarun adds its own repositories on top of Arch's. They are listed first in
/etc/pacman.conf, and that order is what makes an Obarun system an Obarun
system: where a package exists in both, Obarun's version wins.
The Obarun repositories¶
obcore and obextra are Arch's core and extra, holding the packages
from which systemd had to be taken out. That is their role, and it is why they
sit above the Arch repositories: a package that exists in both is taken from
Obarun's, and the Arch one, which would pull systemd in, is never used.
| Repository | Its role |
|---|---|
obcore |
Arch's core, with the packages that had to lose systemd rebuilt without it |
obextra |
Arch's extra, same principle. The Obarun tools happen to live here too: obinstall, pacopts, obarun-mkiso, obarun-zsh |
observice |
The 66 service definitions, one package per daemon, named <daemon>-66serv. No Arch equivalent |
obcommunity |
Community maintained. Not officially supported by Obarun, use at your own risk |
A package you install from obcore or obextra is the Arch package, built from
the Arch recipe, with the systemd dependency removed. Everything Arch ships that
works untouched stays in core and extra and is never duplicated.
Each of the first three has a matching -testing repository, commented out by
default. Uncomment it only if you intend to test packages before they reach the
stable repositories, and expect breakage.
obcommunity plays the role the AUR plays on Arch, with one difference that
changes everything in practice: the built binary is in the repository. You
install it with pacman like any other package. Nothing is compiled on your
machine, there is no PKGBUILD to read and no build to babysit. Contributions
go to
git.obarun.org/pkg/obcommunity.
Then the Arch repositories¶
core and extra follow, through the usual mirrorlist. Everything that works
unchanged without systemd comes from there, at Arch's pace.
multilib is present but commented out. Uncomment it if you need 32-bit
applications on x86_64.
The shipped configuration¶
The repository section of the Obarun /etc/pacman.conf:
#[obcore-testing]
#Server = https://cloud.server.obarun.org/$repo/os/$arch
[obcore]
Server = https://cloud.server.obarun.org/$repo/os/$arch
#[obextra-testing]
#Server = https://cloud.server.obarun.org/$repo/os/$arch
[obextra]
Server = https://cloud.server.obarun.org/$repo/os/$arch
# [obcommunity] is not officially endorsed by Obarun,
# and its use is at your own risk and discretion.
# It is community-managed. You may consider participating
# and contributing to this repository at
# https://git.obarun.org/pkg/obcommunity
#[obcommunity]
#Server = https://cloud.server.obarun.org/$repo/os/$arch
#[observice-testing]
#Server = https://cloud.server.obarun.org/$repo/os/$arch
[observice]
Server = https://cloud.server.obarun.org/$repo/os/$arch
#[core-testing]
#SigLevel = DatabaseOptional
#Include = /etc/pacman.d/mirrorlist
[core]
SigLevel = DatabaseOptional
Include = /etc/pacman.d/mirrorlist
#[extra-testing]
#SigLevel = DatabaseOptional
#Include = /etc/pacman.d/mirrorlist
[extra]
SigLevel = DatabaseOptional
Include = /etc/pacman.d/mirrorlist
Order is not cosmetic
If an Arch repository ends up above an Obarun one, pacman will happily
install the Arch build of a package Obarun rebuilt, and pull systemd back
into your system. When you edit pacman.conf, keep the Obarun blocks on
top.
Service packages¶
Daemons and their 66 services are packaged separately. Installing
cupsd-66serv from observice brings in CUPS and adds the service definition,
so you can go straight to 66 enable -S cupsd.
List them all:
Which repository did this come from¶
See pacopts.