updating some work...

master
brent s. 3 years ago
parent 8d9618cb3b
commit 954a46f1fe
  1. 1
      ARB/main.py
  2. 15
      readme.txt

@ -11,6 +11,7 @@ import repo
# TODO: track which versions are built so we don't need to consistently rebuild ALL packages
# TODO: logging
# TODO: check result of build and *conditionally* cleanup if self.cleanup == True.
# TODO: print repo snippet

_dflts = {'cfgfile': '~/.config/arch_repo_builder/config.xml',
'cache_db': '~/.cache/arch_repo_builder/packages.sqlite3'}

@ -1,10 +1,17 @@
You will need a configuration file for the user performing the building.
Place it at ~/.config/arch_repo_builder/config.xml - you can find an example one in sample.config.xml

But it does require the following packages to be installed, and the buildbox (not the repo mirror server itself) needs to be Arch:
It also requires the following packages to be installed on the buildbox, and the buildbox (not the repo mirror server
itself, necessarily) needs to be Arch:

- pacman (duh)
- devtools
- namcap
- devtools (for https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot)
- pacman
- rsync
- python-gpgme
- python-lxml
- python-paramiko
- python-requests

It is designed to be run as a *non-root* user. Use the regen_sudoers.py script to create a sudoers CMND_ALIAS (https://www.sudo.ws/man/1.7.10/sudoers.man.html) to add for your packaging user.
It is designed to be run as a *non-root* user. Use the regen_sudoers.py script to create a sudoers
CMND_ALIAS (https://www.sudo.ws/man/1.7.10/sudoers.man.html) to add for your packaging user.

Loading…
Cancel
Save