On Tue, Aug 25, 2009 at 2:12 PM, Wesley<email address hidden> wrote:
> I want to second the idea of -dev package as a dependency for libgems
> (or gems) package. I needed to install a gem and I got errors, which
> started with mkmf.
Not all gems require a development environment to install, so I
disagree with any development packages being a dependency. That some
gems require a development environment to install is, in my opinion, a
flaw with the gem model. Those gems that are ultimately necessary
should be natively packaged.
The argument over if ruby1.8-dev should be 'suggests' or 'recommends'
is still open upstream.
On Tue, Aug 25, 2009 at 2:12 PM, Wesley<email address hidden> wrote:
> I want to second the idea of -dev package as a dependency for libgems
> (or gems) package. I needed to install a gem and I got errors, which
> started with mkmf.
Not all gems require a development environment to install, so I
disagree with any development packages being a dependency. That some
gems require a development environment to install is, in my opinion, a
flaw with the gem model. Those gems that are ultimately necessary
should be natively packaged.
The argument over if ruby1.8-dev should be 'suggests' or 'recommends'
is still open upstream.