- The default configuration can be found in
- An optional
config.localmay override the default configuration.
- The path and name of the local configuration file can be overridden by setting the
The executables that you (might) care about are:
dbscripts/ ├── cron-jobs/ │ ├── devlist-mailer │ ├── ftpdir-cleanup │ ├── integrity-check │ └── sourceballs ├── db-move ├── db-remove ├── db-repo-add ├── db-repo-remove ├── db-update └── testing2x
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
Moving packages from testing to stable repositories is such a common
task that we have a wrapper around
db-move to make it easier:
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-remove. So, we have:
Now, we'd like to be able to check that the repos are all OK, so we have
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:
Things that haven't been mentioned yet:
- Install the
dockerpackages. Start the docker daemon by issuing
systemctl start docker.
- The test suite can now be run with
- A coverage report can be generated with
make test-coverage. Open
coverage/index.htmlin your web browser to inspect the results.