Lucas Nussbaum dijo [Wed, Oct 17, 2007 at 11:29:27AM +0200]: > >From what I remember from our rubygems discussions, the conclusion was > that the rubygems package was here for users to install packages, not > for other packages to use it. [0] > > [0] http://pkg-ruby-extras.alioth.debian.org/rubygems.html > > That's why several packages apply patches during build, so they don't > need rubygems anymore. > > However, it's not the case of mongrel: it depends on rubygems. > > Should we fix mongrel, or change our position on rubygems?
Hi, At some point, I tried to get Mongrel to run without Gems. It did not, as Filipe pointed out. Not that I'm too familiar with its internals (even less a couple of months ago)... But it just pushed us away from the upstream code, and was just too much hassle. I never got it to work. I believe we should stick to our position - as it is a strong recommendation. Mongrel does not install any gems by itself, but uses thoroughly the gem_require mechanism. As long as we do keep the dependency information up to date, I do not believe this will matter in the end. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
