Variable: package-vc-allow-build-commands
package-vc-allow-build-commands is a customizable variable defined in
package-vc.el.gz.
Value
nil
Documentation
Whether to run extra build commands when installing VC packages.
Some packages specify "make" targets or other shell commands
that should run prior to building the package, by including the
:make or :shell-command keywords in their specification. By
default, Emacs ignores these keywords when installing and
upgrading VC packages, but if the value is a list of package
names (symbols), the build commands will be run for those
packages. If the value is t, always respect :make and
:shell-command keywords.
It may be necessary to run :make and :shell-command arguments in order to initialize a package or build its documentation, but please be careful when changing this option, as installing and updating a package can run potentially harmful code.
This applies to package specifications that come from your
configured package archives, as well as from entries in
package-vc-selected-packages and specifications that you give
to package-vc-install directly.
This variable was added, or its default value changed, in Emacs 30.1.
Probably introduced at or before Emacs version 30.1.
Source Code
;; Defined in /usr/src/emacs/lisp/emacs-lisp/package-vc.el.gz
(defcustom package-vc-allow-build-commands nil
"Whether to run extra build commands when installing VC packages.
Some packages specify \"make\" targets or other shell commands
that should run prior to building the package, by including the
:make or :shell-command keywords in their specification. By
default, Emacs ignores these keywords when installing and
upgrading VC packages, but if the value is a list of package
names (symbols), the build commands will be run for those
packages. If the value is t, always respect :make and
:shell-command keywords.
It may be necessary to run :make and :shell-command arguments in
order to initialize a package or build its documentation, but
please be careful when changing this option, as installing and
updating a package can run potentially harmful code.
This applies to package specifications that come from your
configured package archives, as well as from entries in
`package-vc-selected-packages' and specifications that you give
to `package-vc-install' directly."
:type '(choice (const :tag "Run for all packages" t)
(repeat :tag "Run only for selected packages" (symbol :tag "Package name"))
(const :tag "Never run" nil))
:version "30.1")