[ruby-core:36021] [Ruby 1.9 - Bug #4594] Don't depend on extension automagic

Issue #4594 has been updated by Yui NARUSE.


Nathan McSween wrote:
> Extensions in ruby are built automatically by what is found at compile time, this is bad as dependencies won't be tracked w.r.t package managers (yum, etc).

If package managers want to manage ruby's bundled extension libraries, split them by package managers.
The NetBSD Packages Collection (pkgsrc) does it.
----------------------------------------
Bug #4594: Don't depend on extension automagic
http://redmine.ruby-lang.org/issues/4594

Author: Nathan McSween
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 
ruby -v: 1.9.2


Extensions in ruby are built automatically by what is found at compile time, this is bad as dependencies won't be tracked w.r.t package managers (yum, etc).

Also ext/Setup as per README reads as if extensions are built based on what is defined in ext/Setup (and logically what should happen), doesn't happen
 4. Remove comment mark(#) before the module names from ext/Setup (or
 add module names if not present), if you want to link modules
 statically.
 
 If you don't want to compile non static extension modules
 (probably on architectures which does not allow dynamic loading),
 remove comment mark from the line "#option nodynamic" in
 ext/Setup.


-- 
http://redmine.ruby-lang.org