public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Mass last-riting of x86-but-not-amd64 packages
Date: Sat, 31 Aug 2019 21:56:44 +0100	[thread overview]
Message-ID: <20190831215644.74792a99@symphony.aura-online.co.uk> (raw)
In-Reply-To: <8696be7bb9d53c8cea7d2accbcd6f6303d0adfa5.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]

On Sat, 31 Aug 2019 10:03:47 +0200
Michał Górny <mgorny@gentoo.org> wrote:

> dev-games/flinker

This builds and starts on amd64 but I'm dubious about whether it would
work correctly in practise. I don't imagine anyone will want to use it.
Best just let it die.

> dev-games/gtkradiant

This has been superseded a few times over and the current fork is
NetRadiant-custom. There is an open bug about the older NetRadiant but
I only dabbled in Quake mapping so never cared enough.

https://bugs.gentoo.org/352981

> dev-games/hlsdk

This is a remnant of the Half-Life server stuff that vapier removed in
2005 with the message "valve sucks at linux". I could say more about it
but nobody cares.

> games-action/battalion
> games-action/fakk2
> games-action/postalplus
> games-arcade/epiar
> games-arcade/gunocide2ex
> games-emulation/mekanix
> games-fps/aaut
> games-fps/industri
> games-fps/red-blue-quake2
> games-fps/tenebrae
> games-fps/tribes2
> games-fps/unreal-tournament-strikeforce
> games-fps/ut2003-bonuspack-cm
> games-fps/ut2003-bonuspack-de
> games-fps/ut2003-bonuspack-epic
> games-fps/wolfgl
> games-misc/c++robots
> games-roguelike/hengband
> games-server/bf1942-lnxded
> games-server/mtavc
> games-strategy/mindrover-demo
> games-strategy/netpanzer

I'll try to look through some of these. I still care about UT and even
worked on (but didn't finish) a new UT99 ebuild not so long ago.
Unfortunately it's never been a top priority.

> sys-fs/atari-fdisk

This is still usable on m68k, which is the Atari's own architecture.
The code assumes 32-bit longs so it won't work on 64-bit but it
probably wouldn't be that hard to fix if someone cared enough. I'm
interested in m68k but for the Amiga rather than the Atari. I'm not
sure how useful this is in practise. On the Amiga, I would still use
the AmigaOS partitioning tool over something like this. There is no
replacement for the Atari on Linux as far as I can see though so I
think it should stay.

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2019-08-31 20:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31  8:03 [gentoo-dev] [RFC] Mass last-riting of x86-but-not-amd64 packages Michał Górny
2019-08-31  8:22 ` Mart Raudsepp
2019-08-31  9:16 ` Roy Bamford
2019-08-31 11:07   ` Nils Freydank
2019-09-01  7:23     ` Michał Górny
2019-08-31 14:39 ` Michael Orlitzky
2019-08-31 20:14 ` Matt Turner
2019-08-31 20:20   ` Michał Górny
2019-09-01  9:46     ` David Seifert
2019-08-31 20:56 ` James Le Cuirot [this message]
2019-09-01  7:50   ` Michał Górny
2019-09-08  9:23 ` Michał Górny
2019-09-08 14:47   ` Ulrich Mueller
2019-09-08 15:20   ` Conrad Kostecki
2019-09-08 15:53     ` Michał Górny

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=20190831215644.74792a99@symphony.aura-online.co.uk \
    --to=chewi@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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