You are not logged in.
Pages: 1
Yes, you read that right. I am actually thinking of switching to a different distribution. The situation with the Current repo has gotten that bad... Really, we are miles behind every distro other than Debian. Arch is not bleeding-edge any more; it has become trailing-edge. The Testing repo isn't quite stable enough to use, but there's plenty of stuff in it (e.g. Gnome 2.12) that is stable enough to move into Current, but hasn't been moved. Why? Sure, it's compiled with GCC 4, but would that even be a problem?
Come to think of it... Why wasn't everything switched over to GCC 4 before libtool-slay, so that we'd have an up-to-date Current branch during the slaying?
Look, sorry if I come across as trollish, or don't quite know what I'm talking about (probably the case), but I think I have a fair reason to be. Maybe Arch will be a viable distro again in a month or two, but as of right now it's very, very far behind where it ought to be.
(Frugalware is starting to look rather attractive...)
Offline
bye
Mr Green
Offline
Dude, I don't mean immediately
Offline
Come to think of it... Why wasn't everything switched over to GCC 4 before libtool-slay, so that we'd have an up-to-date Current branch during the slaying?
Good point.
But...do you realize how impatient this makes you look? It's been a month, that's all! Yes, it would be nice to have a tiny bit of news about when it might be all over but as soon as it is over you'll have the one of the most bleeding edge distros around (again). Surely that is worth waiting? But, if you got nothing better to do than reinstall distros all the time then why even bother posting about it, just get distro hopping.
I assume you hope to elicit some news about when it will all be over and the word is "soon". I have also been informed that there are going to be some changes round here soon...
Everyone should have recognised this period for what it is, a necessary evil. I think it could have been handled much better but regardless of that when it is done it is done and I hope some lessons might be learned.
So, don't bother switching. If the end of libtool slay and gcc was announced on Wednesday along with chalk of new dev positions to get things ticking along you'll be pissed if you switch now!
I am considering a new motto:
"When the going gets tough, the not-so-tough piss off to Ubuntu!"
Lightweights!
Offline
I am considering a new motto:
"When the going gets tough, the not-so-tough piss off to Ubuntu!"
I like it! :twisted:
·¬»· i am shadowhand, powered by webfaction
Offline
It's almost like a soap opera here.
It's not that I don't understand the feelings. It's a difficult job to maintain a distro in your spare time.
A virtual community such as this will never be as good or bad as a work environment. There isn't the same type of commitment. This is also a fairly small community in terms of how many people are involved.
I think it's important to try other distros. I tried Ubuntu, and there were things I liked about it, but after a week I put Arch back.
Dibble is right. The next version of Arch will be righteous.
--HAPS
Offline
Good point, DTW, I suppose I'll stick around - what with the archck kernel and firefox-devel (kudos to iphitus and shadowhand!), it's possible to have a secure system without using Testing.
I am considering a new motto:
"When the going gets tough, the not-so-tough piss off to Ubuntu!"
Urgh. Now that is one distro I am not going to touch.
(Repeat after me: SystemV is evil... SystemV is evil... SystemV is evil...)
Offline
Is actually enabling 'testing' repo such a big hassle?
Not that it's currently unstable or something, just filled with gcc4 and libtool-slayed stuff.
Offline
Most of the stuff there works, but some doesn't.
Offline
and it's no good if you are building pkgs to distribute...as some of us are..including archck (credit please)
Offline
Yep, thanks to you too, DTW.
Offline
I use ubuntu on the desktop, and arch on the server..
you know what they say..
"Man with a foot in two different boats, either very flexible, or gets sore crotch."
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
I don't really know what the point is for having every little thing bleeding edge. It's not like you MUST have the newest apps on your system right away. Don't worry, they're not going anywhere...
Anyway, my point is that it may look like things have slowed down with Arch's dev but infact it's still going rather smoothly from what I can see (maybe I'm blind, or need glasses). Besides, I think it's a good thing that the libslay and GCC 4 transition is being taken so seriously, it should mean good things in the end.
But what do I know.
-- woodstock
Offline
There's nothing wrong with not being bleeding edge... But a distribution should be up-to-date. Updates for things like browsers are usually security updates, and security fixes should be employed whenever possible.
(FWIW, I define "bleeding edge" as "so new it doesn't quite work". That's pretty much what the Testing repo is.)
Offline
Gullible, you do a have a bit of a "thing" about security updates tho don't you, mate? Not to say that is bad but it says alot about why you might be frustrated and I agree with you: there is no reason why a critical update cannot be added to extra during this period, IMO.
Offline
Pages: 1