summaryrefslogtreecommitdiff
path: root/archbuild.in
AgeCommit message (Collapse)Author
2013-04-06Only try to use btrfs snapshots if chroots are on a btrfs partitionPierre Schmitz
2013-03-17archbuild: only use base-devel to new chrootSébastien Luttringer
Since TODO [1] which state: It would be good for base-devel to install everything needed for a build chroot we can remove base and sudo [1] https://www.archlinux.org/todo/add-more-to-base-devel/ Signed-off-by: Sébastien Luttringer <seblu@seblu.net> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2013-01-22archbuild: fix default build flags20130122Pierre Schmitz
2013-01-20Allow makechroot options in archbuildSébastien Luttringer
This will allow, by example, to easily build a package with a custom pkg. staging-x86_64-build -- -cI /var/cache/pacman/pkg/ldoc-1.2.0-1-any.pkg.tar.xz staging-x86_64-build -- -n Signed-off-by: Sébastien Luttringer <seblu@seblu.net> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-11-15Make sure the usage functions are consistentEric Bélanger
The usage messages now begins with a "Usage:", i.e. capitalized and with a colon. Fixes FS#26956. Signed-off-by: Eric Bélanger <snowmaniscool@gmail.com> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-10-03archbuild: abort if update or creation of the chroot failsPierre Schmitz
2012-06-16archbuild: do not cross filesystems when removing the chroot copiesPierre Schmitz
2012-06-16archbuild: use flock -n as we do elsewherePierre Schmitz
2012-06-12archbuild: Store chroots in /var/lib instead of /var/tmpPierre Schmitz
/var/tmp is cleaned up by tmpfiels by default which we cannot handle gracefully.
2012-01-18Set correct pacman.conf20120119Pierre Schmitz
Commit ee4edefa2f12372adb4793c0dd6420fc76911ae4 reverted too much and left pacman.conf unset
2012-01-18Remove any pacman 4 related workarounds20120118Pierre Schmitz
2011-12-04archbuild: exec makechrootpkg to preserve exit valueDave Reisner
This fixes a compound command such as the one below from continuing even if the first fails. extra-x86_64-build && extra-i686-build The problem is that 'cleanup 0' is triggered in archbuild even after an unsucessful call to makechrootpkg. Since both archbuild and makechrootpkg share the exact same cleanup function (from lib/common), we simply force the shell to exit with the true return value by exec'ing the call to makechrootpkg. Signed-off-by: Dave Reisner <dreisner@archlinux.org> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2011-11-06archbuild: Always use recent makepkg.conf and pacman.conf; Run namcap by defaultPierre Schmitz
2011-11-01Move common functions to a shared filePierre Schmitz
* common.sh is included on build time * most functions are copied from makepkg
2011-10-29temporary workaround until pacman 4.0 moves to [core]Pierre Schmitz
Pacman 3 refuses to work with the pacman 4 SigLevel config entry Also related: https://bugs.archlinux.org/task/26555
2011-10-07Support non-standard install locationsLukas Fleischer
This build system overhaul allows for adding (define-style) macros to our scripts. All source files are now suffixed with ".in" to clarify that they might contain unprocessed defines. The Makefile provides a new rule to preprocess source files and generate proper output scripts. Also, add a "@pkgdatadir@" define (as used in GNU Autotools) and use it instead of hardcoded paths to "/usr/share/devtools" everywhere. We missed this when adding PREFIX support to the build system in commit 35fc83ce7d8dc26cd424321f2e8638d05da0a6d4. Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-15 05:05:17 +0000