14:00 <Guest23> Has anyone setup ruby on rails for Arch linux? I wanted to start looking into ruby this way, but I seem to have stumbled into a minor conflict. The ruby-stdlib package already installs rdoc system-wide, but rails installs it as a gem, so I get a scroll of "already initialized constant" warnings any time I invoke "gem". Mind you, I know nothing

14:00 <Guest23> about ruby, but I think this is what's happening.

14:01 <Guest23> I literally just did

14:01 <Guest23> sudo pacman -S ruby ruby-stdlib

14:01 <Guest23> gem install rails

14:01 <Guest23> rails new test-proj

14:04 <Guest23> I tried uninstalling the rdoc gem, but then I can't use the project, because it complains that not all the gems have been installedd

14:04 <Guest23> And I need the stdlib, because it installs a bunch of stuff that's needed all over the place

14:06 <Guest23> I could turn off the warning I presume, but I'd rather find a proper solution. It doesn't look like I can remove the rdoc dependency from the Gemfile, because it's pulled in indirectly.

14:10 <vidyacat> According to comments in the AUR, Rails is in a bad state on Arch: https://aur.archlinux.org/packages/ruby-rails

14:10 <vidyacat> You may be more likely to get help on #archlinux as your questions are specific to it.

14:11 <vidyacat> Bigger channel, more eyes, etc.

14:11 <vidyacat> Consider uninstalling ruby via pacman and DIY your own build?

14:17 <Guest23> I did install rails with gem instead of installing ruby-rails. The wiki says it's the recommended way, and I was hoping I could avoid most issues this way, although evidently that's not the case.

14:18 <Guest23> For a second I thought that installing rails system-wide with ruby-rails could fix the issue, but I did see your link saying that the situation is messy

14:21 <Guest23> I'm new to ruby, so I also wanted to avoid getting into custom build processes since it always means pain, and in my situation probably mega-pain.

14:22 <Guest23> I'll try on the archlinux channel, and if all fails, I'll turn off the warnings and leave the problem to future me

14:23 <Guest23> Isn't DHH playing around with Arch these days though? Surely there must be a clean solution already

14:35 <o0x1eef> Most of the time official Ruby packages are problematic. You might want to look into rbenv and similar tools. They're quite popular nad let you manage multiple rubies. Most of all they don't butcher a standard Ruby install to pieces. And it looks like Arch has done that by separating the stdlib from Ruby itself.

14:38 <o0x1eef> Btw, already initialized constant is not a fatal error in Ruby. Can you provide a backtrace and log?

14:41 <Guest23> Right, a tool like that could be a sensible way to go given the state of things.

14:42 <Guest23> It's not a program of mine crashing: the warning is printed by the "gem" program, and it works. It just complains

14:43 <Guest23> I don't have a trace since there's no crash, and I'm new to everything ruby: I don't know how to get a log from gem

14:43 <o0x1eef> It is safe to ignore that warning

14:44 <Guest23> I prefer getting my warnings sorted usually, but I may just silence gem for the time being...

14:52 <o0x1eef> I mean, it is not normal :) But it is also not a show stopper. So if you have a goal to reach, it shouldn't stop you.

15:05 <Guest23> Thanks for the help