Bug 256074 – Rename x86 tarball to i486

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Allen Brooker (AllenJB) 2009-01-23 11:40:16 UTC]

One of the common mistakes new users make is to select the x86 tarball (eg. stage3-x86-2008.0.tar.bz2) when they really want the i686 tarball. They often then overwrite the default make.conf with the i686 CHOST, which obviously results in problems. To help make the choice clearer, I believe the x86 tarball filename should be changed to i486 instead (ie. stage3-i486-2008.0.tar.bz2 instead of stage3-x86-2008.0.tar.bz2).

[Comment 1 Jeremy Olexa (darkside) (RETIRED) 2009-01-23 15:04:17 UTC]

I concur and did this myself a few weeks ago, I found it slightly annoying.

Hmm, whom should this be assigned to? release team and docs team after a decision?

[Comment 2 Andrew Gaffney (RETIRED) 2009-01-23 16:40:45 UTC]

I've changed the specs in SVN for the autobuilds, so next week's x86 build should reflect this change. CC'ing docs team to let them know

[Comment 3 nm (RETIRED) 2009-01-26 08:55:22 UTC]

Uhhh . . . what about bug 189793? I thought we were shipping i686 as the minimum; that i486 didn't work anymore.

Also, until releng sits down to have a nice long chat with the GDP about how we're going to go about entirely rewriting all our handbooks (when we're all ready for the autobuilds to become the canonical install method), we can't document *anything* about the weekly builds.

[Comment 4 Andrew Gaffney (RETIRED) 2009-01-26 13:27:35 UTC]

Bug 189793 was a fluke. The minimal should support i486 just fine, normally. As for the docs changes, it's probably a good idea to mention the autobuilds in the "live" docs in the section on getting a stage tarball.

[Comment 5 Robin Johnson 2009-08-09 01:14:45 UTC]

This has been done in the autobuilds for a long time now.

[Comment 6 nm (RETIRED) 2009-08-09 07:42:09 UTC]

Marking as a blocker, since the GDP still needs to keep track of renames for the pending handbook updates.