Re:Making Debian Responsible For Its Actions
by halostatue on Tuesday September 28, 2010 @05:32PM
(#1737416)
The proposed solution (an environment variable) is crap. That any of the Debian maintainers think that it's a good idea is an indication of how badly broken the Debian process is, and I know that Lucas was trying to do a good thing there. I don't blame him, it's at least an attempt at a fix.
There's already a working solution provided by Apple for Mac OS X and improved upon by the RubyGems team. There's concepts of vendor gems, system gems, user gems, and I think one other level. The Debian team has never considered it despite being told that it's there. The Debian team has also never offered patches that would help RubyGems come more in line with what Debian thinks it should be doing.
Why should the RubyGems guys bother working with uncooperative Debian maintainers?
Also, if you read the Debian guy's opinion, it is clear that, behind the scenes, and away from all the kerfluffle, people are doing work to improve the situation.
Also, you people seem awfully sure of yourself. If you peruse the bug reports, you might find some interesting nuggets:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588125
> - Do we want to disable gem update --system? I think that we should allow a way for the user to do it anyway.
But don't let me disabuse you of your preconceived notions.