For example in the case of
alpine linux, there are
APKBUILD scripts which reference the source files, the complete source code can be easily fetched with the
abuild fetch command from the
apline-sdk, this does however not include the dependencies required to build and compile the package.
So far I would include the complete source code referenced in the
APKBUILD script, the
APKBUILD script itself and the same for all runtime dependencies.
If I understand the following part of the gplv2 (section 3) correctly providing the build and compile dependencies is not necessary if they can be installed through the package manager from the target operating system (Alpine Linux).
[...]The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.[...]
Do I have to provide the build dependencies listed in a package build script to comply with GPLv2 even if they can be installed through the targeted OS package manager?