Re: Removal of firefox115 and firefox128

[Greg Troxel <gdt%lexort.com@localhost>]

Brad Spencer <brad%anduin.eldar.org@localhost> writes:

> Greg Troxel <gdt%lexort.com@localhost> writes:
>
> [snip]
>
>>   - be prepared to give up on marginal arches for rust, and concentrate
>>     on amd64, aarch64, i386, earmv7hf-el, and consider having a working
>>     rust-bin good enough for the 32-bit arches
>
> [snip]
>
> I assume you are suggesting using rust's ability to create a cross
> compilers.  If the assumption that rust can that well, is true[1], then
> I think that the ONLY architecture that should be compiling the rust
> compiler from source is amd64 and aarch64 and literally everything else
> should be a cross compiler created from one of those two.

I am not entirely suggesting cross, as rust.org releases some binaries.

Whatever can work is great; I'm really suggesting a plan where progress
on the arches that really matter is not held up because of ppc.

While cross is great, I think we need a story to "build" on systems that
are minority arches.  That could be fetching rust-bin and making a
package; by build I mean "make package-install".  I appreciate the "if I
wanted pkgbin I'd use Debian" take, but rust's memory requirements are
just too unreasonable to be feasible on a vast number of computers that
are otherwise fine.

I think we are already doing that.  The big issue is deciding to version
and let support for various arches arrive not in lockstep.