From: Jeremy Olexa <darkside@gentoo.org>
To: "gentoo-alt@lists.gentoo.org" <gentoo-alt@lists.gentoo.org>
Subject: Re: [gentoo-alt] Restructuring the bootstrap (or: getting rid of gcc 4.2)
Date: Sun, 2 Feb 2014 14:12:30 -0600 [thread overview]
Message-ID: <CAMxqorWFY=-8OghVfWrsNeZ4o+QBohNBbVC1DSJ2o8yT1MZacw@mail.gmail.com> (raw)
In-Reply-To: <201402020331.51096.redlizard@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Sat, Feb 1, 2014 at 8:31 PM, Ruud Koolen <redlizard@gentoo.org> wrote:
> Hi all,
>
> I have recently been doing some cleanup work to the bootstrap script,
> getting
> rid of cruft here and there. My goals in this have been twofold: part of
> the
>
I do have to say that I respect your goals here. The essential problem is
that bootstrapping is fragile. We all agree there. However, to introduce a
fundamental change to the process, you will encounter resistance. Now, you
are testing on the "easiest" platform that Gentoo Prefix supports - linux.
Such that there is no automated testing, I'd strongly advise that you start
compiling a list of platforms where the "new" method works. Since you are
the champion of this new idea, it should be your responsibility to ensure
that there is no loss of support. Now, the hard part is that one person
does not have access to many platforms. I would get ahold of SLES 10&11,
which has been historically, the hardest linux flavor to support. Ping Alan
(one of our most active contributors over the years) to see how FreeMiNT
goes. You get some access to solaris from Fabian (but I think there is some
version open sourced?). Of course there is others too..
Does that make sense?
[-- Attachment #2: Type: text/html, Size: 1601 bytes --]
next prev parent reply other threads:[~2014-02-02 20:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 2:31 [gentoo-alt] Restructuring the bootstrap (or: getting rid of gcc 4.2) Ruud Koolen
2014-02-02 9:04 ` Fabian Groffen
2014-02-02 17:34 ` Ruud Koolen
2014-02-02 19:35 ` Fabian Groffen
2014-02-03 9:16 ` Fabian Groffen
2014-02-03 9:43 ` heroxbd
2014-02-03 9:48 ` Fabian Groffen
2014-02-03 9:52 ` Ruud Koolen
2014-02-05 23:55 ` Ruud Koolen
2014-02-06 0:03 ` heroxbd
2014-02-06 8:37 ` Fabian Groffen
2014-02-02 19:55 ` Francois Bissey
2014-02-02 20:41 ` Ruud Koolen
2014-02-03 20:35 ` François Bissey
2014-02-02 20:12 ` Jeremy Olexa [this message]
2014-02-02 20:24 ` Ruud Koolen
2014-02-03 13:11 ` Michael Haubenwallner
2014-02-06 0:03 ` Ruud Koolen
2014-02-03 1:23 ` heroxbd
2014-02-03 1:57 ` Ruud Koolen
2014-02-03 9:40 ` heroxbd
2014-02-03 9:44 ` Fabian Groffen
2014-04-28 4:52 ` Ruud Koolen
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='CAMxqorWFY=-8OghVfWrsNeZ4o+QBohNBbVC1DSJ2o8yT1MZacw@mail.gmail.com' \
--to=darkside@gentoo.org \
--cc=gentoo-alt@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