<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">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 ?</div><div dir="ltr"><br><blockquote type="cite">On 15 Apr 2022, at 11:16 pm, Herby G <herby.gillot@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">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.<div><br></div><div>Maybe it makes sense for this new bootstrap compiler to live in a repository owned by the MacPorts Github org?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 14, 2022 at 6:22 PM Joshua Root <<a href="mailto:jmr@macports.org">jmr@macports.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2022-4-15 02:16 , <a href="mailto:mcalhoun@macports.org" target="_blank">mcalhoun@macports.org</a> wrote:<br>
> As many of you know, the standard Rust compiler is self-hosting.<br>
> The upstream bootstrap compiler only works (unmodified) on 64-bit 10.9+.<br>
> <br>
> There is an attempt to build a bootstrap compiler that runs on older<br>
> systems [1].<br>
> One stumbling block is where to build and store the bootstrap compilers.<br>
> I am afraid I know little about this.<br>
> Github packages, JFrog, other?<br>
> Does anyone have any suggestions?<br>
> <br>
> Thanks,<br>
> Marcus<br>
> <br>
> 1) <a href="https://github.com/macports/macports-ports/pull/14277" rel="noreferrer" target="_blank">https://github.com/macports/macports-ports/pull/14277</a><br>
<br>
It's not really different to hosting any other distfiles; pretty much <br>
anywhere you can make them available is fine. If you have a GitHub repo <br>
where you keep the work that has gone into this, that's an easy place to <br>
keep the files - just create a tag and make a release using that tag, <br>
and you can attach whatever files you like to it.<br>
<br>
- Josh<br>
</blockquote></div>
</div></blockquote></body></html>