[wellylug] Sarge approaching release

[Enkidu]

On Fri, 3 Sep 2004 16:45:52 -0700, you wrote:

>A thought just occurred to me - which version of gcc is shipped with
>Sarge anyway?  I've been using distcc a lot these days with my gentoo
>boxen, and it'd be nice if I could put it on the server to use those
>mostly-idle procs for compiling with...  But distcc requires the same
>minor release of gcc to be on all machines (ie. 3.3.x -> 3.3.x works,
>but not 3.3.x -> 2.95.x which is on my Woody box at the moment)...  If
>Sarge comes with 3.3.x, then that would rock my sox.
>
In my home, up to the minute machine, it's 3.3.4-2 .
>
>On Sat, 04 Sep 2004 11:35:27 +1200, Enkidu <enkidu at cliffp.com> wrote:
>> On Thu, 2 Sep 2004 18:59:41 -0700, you wrote:
>> Fedora? Still uses the old RedHat technologies.
>
>Well, YUM is becoming the default upgrader in these newer releases. 
>It' works quite nicely, but is nowhere NEAR as fast as apt.
>
>> I've never found a broken package on Sid. Currently most of my boxes
>> run Testing/Sid. I've not had any problems with this sort of setup.
>
>More like a broken task.  I've tried upgrading and finding that KDE is
>b0rk3n, etc... The last time that happened it was several weeks before
>a fixed task was pushed out.  I did fix it manually, but it was a real
>PITA. (not a bread pita, but a ... you get the idea)
>
Broken KDE? Is that a disadvantage? <grin> I've seen packages broken
for dependencies, true, but I just leave 'em until the dependency is
fixed. I do remember one case of a package that didn't have a
dependency for a package that it actually needed. THAT can be a pain.

Cheers,

Cliff