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. -Marcus > On Apr 17, 2022, at 6:39 AM, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Apr 16, 2022, at 10:36, Marcus Calhoun-Lopez wrote: > >> Right now, I put them in a release section of a fork of Rust: >> https://github.com/MarcusCalhoun-Lopez/rust/releases >> >> Could a similar fork be created under the auspices of the MacPorts project? > > Yes, it could be. We haven't done that for any other port before so I'm not > sure why it should happen for rust now, but yes, it could be done. > > I think forks don't preserve releases, pull requests, issues, etc. If you > would like those things preserved, you could transfer your repo to the > MacPorts organization. > > All of this presumes that upstream will not accept whatever changes you've > made. Have we already confirmed that that is the case?
