If by "official release tarball" you are referring to what is in the blender/blender <https://github.com/blender/blender> GitHub repo, that tarball is incomplete. It doesn't contain the other 3 parts.
If instead you are referring to the tarball that is provided at https://www.blender.org/download/, then yes, that tarball is complete, in that it contains everything that comes from the split-up parts in GitHub. However, that tarball is located at a very non-standard location, and it's been pretty strongly recommended that I try not to deviate too far from what the vast majority of other ports are doing (i.e. downloading sources from GitHub). Basically, I didn't want to draw any ire from the veteran devs. If you're willing to back me up on a decision to go with the single tarball from blender.org's download webpage, I'd be more than happy to go that route as well. -- Jason Liu On Fri, Jul 17, 2020 at 8:24 PM Joshua Root <j...@macports.org> wrote: > On 2020-7-18 10:02 , Jason Liu wrote: > > You mean on their git server? Yes, the vast majority aren't included in > > the official release tarballs. Repos like "blender-buildbot", > > "blender-org", "blender-dev-fund", etc. are for their buildbot CI > > server, website, etc. Stuff that I'm sure is important to the Blender > > Foundation, but has nothing to do with Blender the software. > > > > Blender the software is made up of a combination of the tarballs from > > the 4 repos I listed. > > I'm just wondering why you can't use the official release tarball > instead of combining four separate ones downloaded from GitHub. > > - Josh >
