From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Gentoo i486 support
Date: Fri, 24 Aug 2018 10:13:42 -0400 [thread overview]
Message-ID: <CAGfcS_m8VwDwztDPn248B2xfYmAj7K5pZJsPZ7x2Xfb1qLv71g@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP40jfhw6znAu5tJjbd58gSw0+W+ZFET59euvCyusKMzQrA@mail.gmail.com>
On Fri, Aug 24, 2018 at 9:57 AM Mike Gilbert <floppym@gentoo.org> wrote:
>
> On Fri, Aug 24, 2018 at 9:19 AM Kent Fredric <kentnl@gentoo.org> wrote:
> >
> > 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?
>
> Sounds like a lot of work for something that will be used by very few people.
>
I think an exp arch is also overkill. How many packages simply can't
be built for i486? I think a profile+masking makes a lot more sense
than an entire new level of QA that touches every ebuild in the tree
because there might be a few packages that don't work on 25 year old
hardware.
--
Rich
next prev parent reply other threads:[~2018-08-24 14:13 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
2018-08-24 13:57 ` Mike Gilbert
2018-08-24 14:13 ` Rich Freeman [this message]
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=CAGfcS_m8VwDwztDPn248B2xfYmAj7K5pZJsPZ7x2Xfb1qLv71g@mail.gmail.com \
--to=rich0@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