Fork of Arch Linux devtools from https://git.archlinux.org/devtools.git
2180aabc81
It's important to ensure the guest has up to date data because updating a chroot after quite some time can potentially rely on updated archlinux-keyring, something which the host machine either kept up to date on or manually fixed, but it kills automation to mess around with chroot configs like that. Alternatively, signed packages added with -I need to work, and we assume the host is configured to accept these. That is *not* a good reason to completely nuke whatever is in the guest, though. A guest might have been manually configured to accept keys which aren't accepted by the host; one example of this happening in practice, is archlinux32 when building 32-bit packages from an archlinux host. The right solution is to append to, rather thna overwrite, the chrooted guest's pacman keyring. To do this, we will use gpg's native facility to dump the keyring from one GNUPGHOME and import it into another. We'd use pacman-key's --import option directly, but this doesn't support passing custom options like --import-options import-local-sigs Finally use pacman-key's native facility to import the trust status from the host. While we are at it, fix a bug where we didn't respect the host's pacman.conf settings for the GpgDir. While it isn't wildly likely a user will choose to customize this, it is a valid and supported use case and we must think about this ourselves. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Levente Polyak <anthraxx@archlinux.org> |
||
|---|---|---|
| doc | ||
| lib | ||
| .gitignore | ||
| .travis.yml | ||
| Makefile | ||
| PKGBUILD.proto | ||
| README.md | ||
| arch-nspawn.in | ||
| archbuild.in | ||
| archco.in | ||
| archrelease.in | ||
| bash_completion.in | ||
| checkpkg.in | ||
| commitpkg.in | ||
| crossrepomove.in | ||
| find-libdeps.in | ||
| finddeps.in | ||
| lddd.in | ||
| makechrootpkg.in | ||
| makepkg-x86_64.conf | ||
| mkarchroot.in | ||
| offload-build | ||
| pacman-extra.conf | ||
| pacman-gnome-unstable.conf | ||
| pacman-kde-unstable.conf | ||
| pacman-multilib-staging.conf | ||
| pacman-multilib-testing.conf | ||
| pacman-multilib.conf | ||
| pacman-staging.conf | ||
| pacman-testing.conf | ||
| rebuildpkgs.in | ||
| sogrep | ||
| zsh_completion.in | ||
README.md
Devtools - development tools for Arch Linux
This repository contains tools for the Arch Linux distribution for building and maintaining official repository packages.
Patches
Patches can be send to arch-projects@archlinux.org or via a pull request on Github. When sending patches to the mailing list make sure to set a valid subjectprefix otherwise the email is denied by mailman. Git can be configured as following.
git config format.subjectprefix 'devtools] [PATCH'
Releasing
- bump the version in the Makefile
- Commit everything as
Version $(date +"%Y%m%d") - Create a new tag
git tag -s $(date +"%Y%m%d") - Push changes
- Upload the source tarball with
make dist upload - Update the package