> On Feb 4, 2021, at 09:11, [email protected] wrote:
>
>
>> Am 08.01.2021 um 15:50 schrieb Ryan Schmidt:
>>
>> On Jan 7, 2021, at 16:26, Andrew Udvare wrote:
>>
>>> Sometimes the release tarball will come with the submodule source
>>> https://github.com/macports/macports-ports/pull/9612#issuecomment-756376258
>>> but this probably depends on the project.
>>
>> If a release tarball doesn't come with everything needed to build the source
>> (i.e. with submodules included), then it's of no use to anyone. So that
>> would be a bug to report to whoever prepared that tarball.
>
> Unfortunately, for GitHub this bug seems to be the default:
> https://github.community/t/create-release-that-contains-submodule/1329. And
> they are apparently not really eager to fix that.
*Automatically-generated* GitHub tarballs ("archive" and "tarball" types, in
the parlance of the github portgroup) do not contain submodules. For that
reason, and others, developers may choose to *manually generate* a tarball that
contains submodules and anything else necessary and upload that to the GitHub
Release object ("release" type, according to github portgroup). A developer who
manually creates and uploads such a tarball but fails to include submodules or
other necessary files does nobody any favors. That's what I was saying. I was
not referring to automatically-generated tarballs.
