Barrapunto

Added the following test packages that we're not ready to merge in yet:
testing/packages/gcc-3.3/gcc-3.3-i486-1.tgz: This is GCC 3.3, compiled for
    a minimum CPU target of i486. Why i486 and not i386? Because the shared
    C++ libraries in gcc-3.2.x will require 486 opcodes even when a 386 target
    is used (so we already weren't compatible with the i386 for Slackware 9.0
    and nobody noticed :-). gcc-3.3 fixes this issue and allows you to build a
    386 compiler, but the fix is done in a way that produces binaries that are
    not compatible with gcc-3.2.x compiled binaries and which suffer a
    performance hit. To retain compatibility with Slackware 9.0, we'll have to
    use i486 (or better) as the compiler target for gcc-3.3. Therefore, it is
    time to say goodbye to i386 support in Slackware. I've surveyed 386 usage
    online, and the most common thing I see people say when someone asks about
    running Linux on a 386 is to "run Slackware", but then they also usually go
    on to say "be sure to get an OLD version, like 4.0, before glibc, because
    it'll be more efficient." Now, if that's the general advice, then I see no
    reason to continue 386 support in the latest Slackware (and indeed it's no
    longer easily possible). People with 386 machines aren't going to have the
    hard drive space for Slackware 9.1 in any case.