http://bugzilla.opensuse.org/show_bug.cgi?id=1069441 http://bugzilla.opensuse.org/show_bug.cgi?id=1069441#c9 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |ammartinez@suse.com, | |dmacvicar@suse.com, | |fkobzik@suse.com, | |ikapelyukhin@suse.com, | |jordimassaguerpla@gmail.com Component|Ruby |Ruby Version|Current |Leap 15.0 Product|openSUSE Tumbleweed |openSUSE Distribution Target Milestone|--- |Leap 15.0 Summary|[Build 20171121] rails test |getting rails to work on |fails: Could not find gem |openSUSE is cumbersome |capybara | --- Comment #9 from Ludwig Nussel <lnussel@suse.com> --- Moving over to Leap as this test is still red and getting rails to work sucks big time still. The work flow that works is # zypper -n in -C "rubygem(rails)" # zypper in gcc make ruby2.5-devel libxml2-devel glibc-devel libxslt-devel sqlite3-devel $ rails new mycoolapp --skip-bundle --skip-test $ cd mycoolapp $ bundle config build.nokogiri --use-system-libraries $ bundle install --path vendor/bundle $ rails server -b 0.0.0.0 That is far away from obvious and plug&play, at least not to me. So question to the rails folks. Is that work flow expected and well known? If not, how about documenting it in the wiki and/or release notes? Moreover, can we make that easier? For example, there already is a devel_ruby pattern. Would it make sense to just add the aforementioned devel package requirements to this pattern, so instead of installing the rails gem we document installing the pattern instead? Also, can the nokogiri config be made default? -- You are receiving this mail because: You are on the CC list for the bug.