Fork of Arch Linux devtools from https://git.archlinux.org/devtools.git
e963b6da9e
We don't want to check against the current version known to the host
system, because that will be incorrect in a wide variety of situations,
including:
- the build host hasn't done a full system upgrade yet
- we're building against staging, and want to see the delta between
different staging versions
- we're building against extra, but the host runs testing which carries
changes we don't want to visualize right now
- the chroot has a configured database not available to the host, and
the package is only available there
Essentially, it's rarely 100% correct to run checkpkg on the host, but
we already have a database we *know* is correct, and that is the one we
just built the package against. So let's use that.
This also fixes a bug in the current logic, where in order to try
downloading fresh databases, we work in a non-cached temporary working
database to download the package files, but then let checkpkg default to
comparing packages in the system database. Since we are explicitly
trying to compare against packages that differ from the host's pacman
database, we need to pass the package files as options to checkpkg,
using the additional modes added in commit
|
||
---|---|---|
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 | ||
makerepropkg.in | ||
mkarchroot.in | ||
offload-build.in | ||
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.in | ||
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