For the official Rust compiler, we are assured it comes from the official rust-lang Github repository.
Rust is a critical build chain component just like gcc is. Introducing a bootstrap compiler means that we are introducing an external element that has the ability to potentially modify Rust itself, as well as all downstream Rust software in MacPorts. So in my mind, it makes the most sense to take extra care in how we build, verify and host such a component. On Sat, Apr 16, 2022 at 11:21 AM Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > Maybe i am missing some detail here, but why cannot this bootstrap > compiler just be a port like everything else, and thus the binary hosting > is just the same as any other binary tarball macports distributes ? > > On 15 Apr 2022, at 11:16 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> wrote: > >> On 2022-4-15 02:16 , 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 >> >> 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 >> >
