Right now, I put them in a release section of a fork of Rust: https://github.com/MarcusCalhoun-Lopez/rust/releases <https://github.com/MarcusCalhoun-Lopez/rust/releases>
Could a similar fork be created under the auspices of the MacPorts project? -Marcus > On Apr 15, 2022, at 3:15 PM, Herby G <herby.gil...@gmail.com> wrote: > > Since this would be adding a component that affects the build of a very core > build component to many MacPorts packages, perhaps a bit more care should be > taken with where it will be stored. > > Maybe it makes sense for this new bootstrap compiler to live in a repository > owned by the MacPorts Github org? > > On Thu, Apr 14, 2022 at 6:22 PM Joshua Root <j...@macports.org > <mailto:j...@macports.org>> wrote: > On 2022-4-15 02:16 , mcalh...@macports.org <mailto:mcalh...@macports.org> > wrote: > > As many of you know, the standard Rust compiler is self-hosting. > > The upstream bootstrap compiler only works (unmodified) on 64-bit 10.9+. > > > > There is an attempt to build a bootstrap compiler that runs on older > > systems [1]. > > One stumbling block is where to build and store the bootstrap compilers. > > I am afraid I know little about this. > > Github packages, JFrog, other? > > Does anyone have any suggestions? > > > > Thanks, > > Marcus > > > > 1) https://github.com/macports/macports-ports/pull/14277 > > <https://github.com/macports/macports-ports/pull/14277> > > It's not really different to hosting any other distfiles; pretty much > anywhere you can make them available is fine. If you have a GitHub repo > where you keep the work that has gone into this, that's an easy place to > keep the files - just create a tag and make a release using that tag, > and you can attach whatever files you like to it. > > - Josh
