Arch Linux

mjevans

Member

Registered: 2010-10-26

Posts: 3

Configure AUR to always skip test? GLOBAL PACKAGE OPTIONS -> specific?

Is it possible to configure AUR to always skip tests for some packages?

For some reason python2 is being pulled in on most of my Arch systems by other packages I'm using, and unlike the old days it's now an AUR package rather than a prebuilt.  Whenever it updates there are a TON of long running and also some seriously annoying (plays audio) tests.

#/etc/makepkg.conf
...
# GLOBAL PACKAGE OPTIONS
#   These are default values for the options=() settings
...

Implies that package specific options may exist, but skipping tests appears to be an all or nothing thing per (in my case yay) command invocation.

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,400

Website

Re: Configure AUR to always skip test? GLOBAL PACKAGE OPTIONS -> specific?

########################################################################
# BUILD ENVIRONMENT
#########################################################################
#
# Defaults: BUILDENV=(!distcc !color !ccache check !sign)
#  A negated environment option will do the opposite of the comments below.
#
#-- distcc:   Use the Distributed C/C++/ObjC compiler
#-- color:    Colorize output messages
#-- ccache:   Use ccache to cache compilation
#-- check:    Run the check() function if present in the PKGBUILD
#-- sign:     Generate PGP signature file
#
BUILDENV=(!distcc color !ccache check !sign)

---

PGP Key: F99FFE0FEAE999BD

mjevans

Member

Registered: 2010-10-26

Posts: 3

Re: Configure AUR to always skip test? GLOBAL PACKAGE OPTIONS -> specific?

Per package BUILDENV then, For example, the default BUILDENV is as you just quoted.

Can it be specified PER PACKAGE somewhere?  So over-ride the global value (In configuration files, not at invocation time!) with E.G.
/etc/makepkg.d/python2 : BUILDENV=(!distcc color !ccache !check !sign)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,550

Website

Re: Configure AUR to always skip test? GLOBAL PACKAGE OPTIONS -> specific?

If it's specific to a package, put it in the PKGBUILD.

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman