9front - general discussion about 9front
 help / color / mirror / Atom feed
From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] mk for only supported archs
Date: Wed, 18 Aug 2021 15:47:50 -0700	[thread overview]
Message-ID: <458C4D0BE90DDD6D8FB2DF22E23182C9@smtp.pobox.com> (raw)
In-Reply-To: <0D783F89C5F8073B9359618EE346C5C1@eigenstate.org>

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.


      reply	other threads:[~2021-08-18 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 14:00 unobe
2021-08-17 15:53 ` Amavect
2021-08-17 20:15   ` unobe
2021-08-21  8:27     ` unobe
2021-08-22 14:15       ` cinap_lenrek
2021-08-22 14:33       ` cinap_lenrek
2021-08-22 15:13         ` Amavect
2021-08-18  3:00 ` ori
2021-08-18 22:47   ` unobe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=458C4D0BE90DDD6D8FB2DF22E23182C9@smtp.pobox.com \
    --to=unobe@cpan.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).