If this was IRC, I would have banned some of the posters here.
]]>someone should lock this
Good idea.
Also, there is still the list of packages to install manually on the first page of this thread while this is being fixed.
Thats why, the person that removed it (kth5 should have had a workaround before mindlessly and brainlessly deleting xorg. Jut as iphitus said. I just find it so logical. Because now we are just bound to complain at cerebral since kth5 just wiped his hands out of this and left other devs take care of his mess.
Why the shameless arrogance?
]]>I feel for the developers and maintainers that have to deal with some of the comments made in this thread. For those of you that don't understand how Linux (and Arch Linux in particular) works, here's a little run down for ya. These guys spend hundreds of hours compiling and maintaining hundreds of packages in their FREE time, and FREE of charge, so that you can use a FREE operating system on your computer.
I have nothing but the utmost respect for the people that contribute to this community and frankly I'm appalled by the poor attitude displayed here by some users. If you need immediate results and/or satisfaction guaranteed, you should drop Arch and switch to a commercially supported OS, such as Windows, OSX, or Ubuntu.
I just had to get that off my chest... thank you, Cerebral for looking into it.
Oh man, thanks a lot for this, I was going to say something, but you just did it much better than me.
]]>There are other packages that are now failing due to the xorg dependency and I have only a little time to resolve the issues that I'm dealing with.
If you're having trouble with packages with the xorg dep - that's an error with the packages (and they will be fixed - I planned to look at them tonight after work). In the meantime, a hack-workaround would be to check their deps (with pacman -Si package), ensure you have all the deps except xorg with pacman -S, then install the broken package with pacman -Sd to ignore depchecks.
It sucks, and I'm sorry for that. I'll see about getting those broken packages fixed tonight.
]]>I have nothing but the utmost respect for the people that contribute to this community and frankly I'm appalled by the poor attitude displayed here by some users. If you need immediate results and/or satisfaction guaranteed, you should drop Arch and switch to a commercially supported OS, such as Windows, OSX, or Ubuntu.
I just had to get that off my chest... thank you, Cerebral for looking into it.
]]>mrblister wrote:It can be killed in 30 seconds but takes 3 days of discussion to put it back up? Oughtta get you guys working for the government. Thats what I call red tape!
I'm trying to be nice here - I'd appreciate the same courtesy in return. I didn't cause this problem, and I'm trying to get it resolved in the way it should properly be done. I apologize if that takes time to do considering we're all just volunteers working on Arch in what time we have.
You arent the one who did it and I understand your frustration. I apologize for my tone, you must understand it isnt directed at you. However, you must understand my frustration as well. There are other packages that are now failing due to the xorg dependency and I have only a little time to resolve the issues that I'm dealing with.
Anyhow. Last thing I'll say on the matter.
]]>It can be killed in 30 seconds but takes 3 days of discussion to put it back up? Oughtta get you guys working for the government. Thats what I call red tape!
I'm trying to be nice here - I'd appreciate the same courtesy in return. I didn't cause this problem, and I'm trying to get it resolved in the way it should properly be done. I apologize if that takes time to do considering we're all just volunteers working on Arch in what time we have.
]]>sickhate wrote:by the why are arch devs planing to kill all metapackages...gnome and bla bla....JESUS!!!! just leave xorg as it was !!! dammmm...
Gnome and so on are not metapackages. They're groups. There's a difference. Please calm down, this will get resolved, and in the proper way. There's discussion going on on the dev-public list. It's just an xorg package - take it easy.
It can be killed in 30 seconds but takes 3 days of discussion to put it back up? Oughtta get you guys working for the government. Thats what I call red tape!
]]>Misfit138 wrote:
Wow, I thought it might have been replaced by now due to public outcry, but I guess it's gone. I'll update the Beginner's guide in the wiki later with a new procedure as soon as I figure out one.whats does it have to figure its going to be just looong typing just to get xorg..
Oops. You seem to be right, I didn't catch that at first glance.-I've been busy and should have taken my time and read everything before jumping the gun. I'll update the wiki the first chance I get with the pacman -S command.
EDIT: Updated Beginner's Guide in the wiki.
]]>shen wrote:I am curious if there is any discussion in the dev circle to put this package back into the repos?
A thread was started on arch-dev-public :
http://www.archlinux.org/pipermail/arch … 01515.htmlit appears there is a migration issue with these xorg and xorg-clients meta packages :
http://www.archlinux.org/pipermail/arch … 01522.html
Good deal, guess I should have looked there first..Thanks for the links.
]]>by the why are arch devs planing to kill all metapackages...gnome and bla bla....JESUS!!!! just leave xorg as it was !!! dammmm...
Gnome and so on are not metapackages. They're groups. There's a difference. Please calm down, this will get resolved, and in the proper way. There's discussion going on on the dev-public list. It's just an xorg package - take it easy.
]]>