From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 9963 invoked from network); 18 Aug 2021 22:56:44 -0000
Received: from 1ess.inri.net (216.126.196.35)
  by inbox.vuxu.org with ESMTPUTF8; 18 Aug 2021 22:56:44 -0000
Received: from pb-smtp1.pobox.com ([64.147.108.70]) by 1ess; Wed Aug 18 18:48:03 -0400 2021
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1])
	by pb-smtp1.pobox.com (Postfix) with ESMTP id EA09DD8B04
	for <9front@9front.org>; Wed, 18 Aug 2021 18:47:52 -0400 (EDT)
	(envelope-from unobe@cpan.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id
	:to:subject:date:from:in-reply-to:mime-version:content-type
	:content-transfer-encoding; s=sasl; bh=Mzfatvq2m3ZtFRAWGMzrzgmyz
	wP+xo5cp7PHGktHmRA=; b=e8+TpQwhLsLFW3NMDk6vb2l4Kly7BympqSzMS+bdM
	/DPJ/f9lwZsHUohwZsXGBXgUR2pcxPtp7QsEKCSChB1Vbj5Adw0bZYpdpaMVa7RG
	M1Vv4QtDgezXNBJRcdAHaXEzqOL56gs4klKt2D3JpX1y0gV9JuPzyd0cdg7t6Mqh
	qA=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1])
	by pb-smtp1.pobox.com (Postfix) with ESMTP id E21D6D8B03
	for <9front@9front.org>; Wed, 18 Aug 2021 18:47:52 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Received: from strider (unknown [47.34.135.186])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 36342D8B01
	for <9front@9front.org>; Wed, 18 Aug 2021 18:47:52 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Message-ID: <458C4D0BE90DDD6D8FB2DF22E23182C9@smtp.pobox.com>
To: 9front@9front.org
Date: Wed, 18 Aug 2021 15:47:50 -0700
From: unobe@cpan.org
In-Reply-To: <0D783F89C5F8073B9359618EE346C5C1@eigenstate.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID:
 51FBBDFE-0076-11EC-B7AF-8B3BC6D8090B-09620299!pb-smtp1.pobox.com
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: stable information database 
Subject: Re: [9front] [PATCH] mk for only supported archs
Reply-To: 9front@9front.org
Precedence: bulk

Quoth ori@eigenstate.org:
> Quoth unobe@cpan.org:
> > http://fqa.9front.org/fqa1.html#1.2 states the supported archs.
> > However, clean and nuke also remove build files for 0 (spim) and q
> > (power).  'mk all' using those archs fails; 'mk kernels' also tries to
> > build all the kernels, even those which are not supported.  For
> > example, I tried to build the power arch (qc, qa, ql) and without
> > surprise it failed (when building dtracy): ...
> 
> Maybe it's worth talking about deleting
> the code to support them, if nobody has
> hardware to test...
> 

QEMU can emulate PPC, so maybe a requirement that someone have
hardware to test is setting the bar high?  My introduction to Plan 9
was via emulation because newer hardware was not supported well, at
all.

> The code will still be in history if anyone
> wants to resurrect it.

If it's in git history, then there's zero cost *not* deleting it, save
someone tries to use it, right?  And in that case, the cost is
localized to the person using it.

Generally (for software in the distribution) my take is that things
should not be removed unless broken beyond repair OR superseded by
something better (so for the latter there's not really a removal, but
a replacement).  For example:

1.  zuke replaced juke: yay!
2.  Nail replaced Mail: yay!
3.  fossil was removed but wasn't replaced with something better.

I'm certain this isn't everyone's take, but it's like, just my
opinion, man. And opinions can change.