As far as I can tell, this was never used.
In commit 9b56647abc8dc33bf138d4b260b103c8d9265b7d the parsepkgbuild
script was switched from defining a PATH as a directory in /tmp, to
actually passing in a PATH=/dummy to `env -i`... which makes sense as
the defined PATH did not used to be used.
It is now possible to use b2sums to verify file integrity. See
https://git.archlinux.org/pacman.git/commit/?id=e03752e6adc86cbb4cb4f52a38f6e3e98cbe9dd5
Signed-off-by: Eli Schwartz
---
Namcap/rules/arrays.py | 9 +
Namcap/rules/extravars.py | 9 +
When listing out the contents of a variable, use loops and references
to the variables in order to reduce code and make it easier to extend.
In the future, a new metadata type can be added simply by appending to
meta_keys=()
Signed-off-by: Eli Schwartz
---
parsepkgbuild.sh | 127
Just as it is unnecessary to run certain commands in a post_upgrade
script, if a hook already runs it, so too is it usually unnecessary to
depend on the package that installs the hook.
Sometimes these dependencies are left in even when the install script is
removed, because people lack
On 4/10/19 9:15 PM, Eli Schwartz wrote:
> Arch Linux now has pacman hooks that provide automatic handling for
> update-{desktop,mime}-database without each package requiring a hard
> dependency and a post_upgrade hook. This means it is no longer correct
> to depend on the packages or provide an
Arch Linux now has pacman hooks that provide automatic handling for
update-{desktop,mime}-database without each package requiring a hard
dependency and a post_upgrade hook. This means it is no longer correct
to depend on the packages or provide an install script. Instead, remove
this entirely.
