43db1c25dc
Adds support for Go modules by detecting a go.mod file and, if available, using it. In addition, to continue supporting vendoring (and avoid the need for git on all module builds), if a package includes a vendor directory, the module mode will switch to vendor mode if not already set. This will use vendored source code for dependencies instead of downloading that code again using the descriptions under go.mod. go_mod_mode=vendor also skips the go.sum check because nothing is downloaded that isn't already verified, so this fixes packages with vendored code that have checksum mismatches due to Go 1.11.4 module checksum changes. [ci skip] Closes: #6036 [via git-merge-pr] |
||
---|---|---|
.. | ||
R-cran.sh | ||
README | ||
cargo.sh | ||
cmake.sh | ||
configure.sh | ||
fetch.sh | ||
gem.sh | ||
gemspec.sh | ||
gnu-configure.sh | ||
gnu-makefile.sh | ||
go.sh | ||
haskell-stack.sh | ||
meson.sh | ||
meta.sh | ||
perl-ModuleBuild.sh | ||
perl-module.sh | ||
perl6-dist.sh | ||
python-module.sh | ||
python2-module.sh | ||
python3-module.sh | ||
qmake.sh | ||
ruby-module.sh | ||
scons.sh | ||
slashpackage.sh | ||
waf.sh | ||
waf3.sh |
README
BUILD STYLES ============ These shell snippets provide support for multiple build systems, i.e GNU configure, CMake, etc. A build style file must provide at least the following functions: - do_configure - do_build - do_install If a source package defines its own do_xxx() function, the function defined in the build style file is simply ignored.