Re: Archive and Binary Swarm distributions: change strategy?

[Ginger Booth]

Is this perhaps the crux of the problem, that Swarm should back up to
using GCC 2.7.2 as a least-common-denominator?  Or if Swarm actually
requires GCC 2.8.x, then say so and require upgrading before installing
Swarm?  Though I understand your suggestion, Paul, I also know how truly
difficult those compiles are.  That's how the current trend got
launched.  Many (most?) potential Swarm users could not pay the door fee
of compiling and configuring the prerequisite software.

You know, much as I might have wished another OS had won the standard,
I'm all for Win32 globalization now.  As an applications programmer, I
think they're all, er, imperfect, and would rather pick One....  Heresy,
I know...

My 2 bits...
        Ginger


Paul E. Johnson wrote:

> Note that the original idea behind the binary install was that users can be
> shielded from the task of changing system software (such at tcl/tk).
> However, when the Swarm binary is distributed as compiled against GCC2.8, 
> while
> users of "standard" linux distributions are using GCC2.7.2, there are
> inevitable problems.  The binary distribution
> does not really save the user from the obligation of making some very big
> changes in the OS. In fact, I'd rather install tk/tcl than swap out GCC.

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.
                  ==================================