1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
# Parabola GNU/Linux-libre repository management scripts
## Requirements
Beyond the `base` package group, dbscripts needs:
* librelib (at least version 20180428)
* rsync
* expac
## Configuration
* The default configuration can be found in `config`.
* An optional `config.local` may override the default configuration.
* The path and name of the local configuration file can be overridden
by setting the `DBSCRIPTS_CONFIG` environment variable.
## Overview
The executables that you (might) care about are:
dbscripts/
├── cron-jobs/
│ ├── db-cleanup [Parabola only]
│ ├── devlist-mailer
│ ├── ftpdir-cleanup
│ ├── integrity-check
│ ├── make_repo_torrents [Parabola only]
│ └── sourceballs
├── db-check-nonfree [Parabola only]
├── db-check-package-libraries [Parabola only]
├── db-check-repo-sanity [Parabola only]
├── db-check-unsigned-packages [Parabola only]
├── db-check-unsigned-packages.py [Parabola only]
├── db-import-archlinuxarm-src [Parabola only]
├── db-import-any [Parabola only]
├── db-import-pkg [Parabola only]
├── db-import-keyring [Parabola only]
├── db-init [Parabola only]
├── db-move
├── db-remove
├── db-repo-add
├── db-repo-remove
├── db-update
└── testing2x [Arch Linux only]
Ok, now let's talk about what those are.
There are 3 "main" programs:
- `db-update` : add packages to repositories
- `db-remove` : remove packages from repositories
- `db-move` : move packages from one repository to another
Of course, sometimes things go wrong, and you need to drop to a
lower-level, but you don't want to go all the way down to pacman's
`repo-add`/`repo-remove`. So, we have:
- `db-repo-add`
- `db-repo-remove`
Now, we'd like to be able to check that the repos are all OK, so we
have
- `cron-jobs/integrity-check`
Instead of enhancing `integrity-check`, Parabola developers have
decided to write multiple stand-alone tools that should probably be
merged into `integrity-check`
- `db-check-*`
When we remove a package from a repository, it stays in the package
"pool". We would like to be able to eventually remove packages from
the pool, to reclaim the disk space:
- `cron-jobs/ftpdir-cleanup`
- `cron-jobs/db-cleanup`
Both of these programs do the exact same thing. Parabola developers
decided to write their own from scratch, instead of modifying
`ftpdir-cleanup`. They should eventually be merged.
But, Parabola doesn't just publish our own packages, we also import
packages from elsewhere:
- `db-import-pkg`
- `db-import-keyring`
- `db-import-archlinuxarm-src`
`db-import-pkg` is the main import program, and it handles importing
most of the binary packages, as well as the source-packages from Arch
Linux. `db-import-keyring` is a specialized variant of it for
importing the "archlinuxarm-keyring" and "archlinux32-keyring"
packages, since those packages need special treatment to end up on the
nescessary architectures. `db-import-archlinuxarm-src` is supposed to
import the source-packages from Arch Linux ARM, but it has been
defunct for some time now and needs updated. There is currently no
program to import source-packages from Arch Linux 32.
Things that haven't been mentioned yet:
- `cron-jobs/devlist-mailer`
- `cron-jobs/make_repo_torrents`
- `cron-jobs/sourceballs`
- `db-init`
## Testing
The test suite is run with a simple `make check` command... except
that it requires you to first fiddle with the system pacman keyring.
See the `test/README.md` file for more details.
|
