From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo i486 support
Date: Sat, 25 Aug 2018 01:19:45 +1200 [thread overview]
Message-ID: <20180825011945.254bb9ca@katipo2.lan> (raw)
In-Reply-To: <5cc35530-3d96-1a0f-b484-73ea3d58bed5@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Wed, 22 Aug 2018 07:26:24 -0500
Ben Kohler <bkohler@gentoo.org> wrote:
> Thoughts?
Is there a good reason we can't have a legacy profile for this?
Or perhaps, a new (exp) arch entirely dedicated to legacy x86?
The latter would be ideal for ensuring everything we *claim* works on
i486 does indeed work there, and making it blatantly obvious what does
and doesn't work on i486.
And both strategies make it possible to restrict USE graphs to subsets
that can only work on i486.
The benefit of a new profile for x86 is it would assume everything
currently x86 works on i486, and then exceptions can be shot on a
case-by-case basis.
But that's also the downside, you start with a huge set and play
whack-a-mole with it, when ideally, you want to start with a *minimal*
working subset and build it out ( and this is where the second option
is better )
The arch-approach would also lend itself to compile-time switching in
individual packages too.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-24 13:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 12:26 [gentoo-dev] Gentoo i486 support Ben Kohler
2018-08-22 13:08 ` Rich Freeman
2018-08-22 13:23 ` Mart Raudsepp
2018-08-22 14:22 ` Peter Stuge
2018-08-22 20:27 ` R0b0t1
2018-08-22 20:39 ` Rich Freeman
2018-08-25 11:07 ` Andrew Savchenko
2018-08-22 13:21 ` James Le Cuirot
2018-08-22 14:30 ` Mike Gilbert
2018-08-22 15:27 ` Thomas Deutschmann
2018-08-22 19:20 ` Matt Turner
2018-08-22 19:27 ` M. J. Everitt
2018-08-22 20:19 ` Richard Yao
2018-08-24 13:19 ` Kent Fredric [this message]
2018-08-24 13:57 ` Mike Gilbert
2018-08-24 14:13 ` Rich Freeman
2018-08-24 14:40 ` Kent Fredric
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=20180825011945.254bb9ca@katipo2.lan \
--to=kentnl@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