chiark / gitweb /
Patch before running prebuild commands.
authorPaul Sokolovsky <pfalcon@users.sourceforge.net>
Fri, 24 Feb 2012 01:21:00 +0000 (03:21 +0200)
committerPaul Sokolovsky <pfalcon@users.sourceforge.net>
Fri, 24 Feb 2012 01:21:00 +0000 (03:21 +0200)
commite1c85dfc21a481c8b29d17b9dfa347cf9558782a
treedd2c7a2129343b9db9a2f351a42381327b5e5bc4
parentea985430b03b53af3d102c530b81178eaa63ca66
Patch before running prebuild commands.

Sometimes an application provides a script to initialize its build
environment, and it may be required to patch such a script before running
it (typical case is hardcoding developer's local paths). More generally,
"declaritive" ways of changing code (e.g., forceversion, patch, etc.)
should be preferred to prebuild, which should be used as the last resort
(as it is too generic and thus verbose). So, it's right ordering in that
respect either.
common.py