Re: Why NOARCH packages aren't available on all architectures?

On 2022-Aug-6, at 16:53, Mark Millard <marklmi@yahoo.com> wrote:

> On 2022-Aug-6, at 15:19, Tatsuki Makino <tatsuki_makino@hotmail.com> wrote:
> 
>> . . .
> 
> https://pkg-status.freebsd.org/?all=1&type=package shows that
> the most recent build for a powerpc* was for powerpc64 and
> started last year: Thu, 20 May 2021 07:08:04 GMT.
> 
> Do not expect anything more modern for the likes of powerpc64.
> 
> By contrast, mips64 has been getting builds with zero built.
> The most recent build with a non-zero number built started
> over 1/2 year ago, on Thu, 27 Jan 2022 02:30:02 GMT.
> 
> mips (non-64) goes back to starting on Thu, 31 Dec 2020 01:03:30 GMT.
> . . .

In some respects the above examples show another limitation
of a NO_ARCH use when it depends on things that are not NO_ARCH
but the platform is not having its port builds generally kept up
to date: Even a NO_ARCH port can be limited to working with only
a finite subrange of potential versions of ports it is dependent
on. The lack of updates to port builds can mean that the
prerequisite packages needed are not available from the servers.

===
Mark Millard
marklmi at yahoo.com