Location to store binaries

[mcalhoun at macports.org]

Sorry, I misunderstood.

Cargo and the Rust Standard Library, which are both required to build Rust, have higher requirements than Rust itself.
Back to 10.7, MacPorts gets around this by using, e.g., the MacPorts build of OpenSSL instead of the CommonCrypto system library.
Prior to 10.7, MacPorts would (if the pull requests are merged) use a patched version of Clang to force emulated thread-local-storage on the bootstrap compiler.

I think it unlikely upstream would be willing to host such a build since I am not sure how to create it outside of the MacPorts ecosystem.

-Marcus

> On Apr 17, 2022, at 7:03 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> On Apr 17, 2022, at 08:45, Marcus Calhoun-Lopez wrote:
> 
>> I have been careful to submit all changes upstreams.
>> So far, most of them have been merged already.
>> The only changes I have not submitted are the ones that apply to systems prior to 10.7, which Rust does not support.
>> These patches are small and can easily be kept as patch files within the port.
>> 
>> However, that is not the reason for the fork.
>> The fork would *only* be for the Release feature of gitbub that allows the upload of binaries.
>> Specifically the upload of the bootstrap compilers for unsupported systems.
> 
> I understand that. If you were able to submit all of your fixes to upstream, then presumably it would be possible for them to build the next version of their bootstrap compiler in a way that was compatible with older systems and then maintaining your fork would not be necessary. That's why I asked.