Package: ruby
Version: 1:1.9.3.4
Severity: normal

I'm a Debian testing user who is new to Ruby. I tried to install jekyll
using
the gem command, and received an error about mkmf that I found very
confusing.
I only figured out what the problem was by searching the web for answers
until
I realized I needed to install ruby-dev. The description of ruby-dev
acknowledges that it is required to build many gems. I feel that a user
experience like this is a hard sell for users of other operating systems.

I can think of three ways to fix this (not all of which may be feasible):

- Split gem into its own package (if this is feasible), and make it depend
on
ruby-dev
- Merge ruby-dev into ruby
- Patch gem to offer to install ruby-dev when a user attempts to install a
gem
that requires mkmf



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable'),
(500, 'oldstable'), (102, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL
set to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ruby depends on:
ii  ruby1.9.1  1.9.3.484-2

ruby recommends no packages.

Versions of packages ruby suggests:
pn  ri        <none>
ii  ruby-dev  1:1.9.3.4



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable'),
(500, 'oldstable'), (102, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ruby depends on:
ii  ruby1.9.1  1.9.3.484-2

ruby recommends no packages.

Versions of packages ruby suggests:
pn  ri        <none>
ii  ruby-dev  1:1.9.3.4

-- no debconf information

Reply via email to