Issue #6051 has been updated by John Ellson.


I can see the need to support parallel installs of versions of the ruby interpreter on a host to support existing scripts.

I don't see the need to support multiple development environments on a single host for developers writing new extensions.  IMO the .pc file should describe the preferred version, typically the latest version.

Perhaps the ruby.pc file could be in a ruby-versioned location with the latest one softlinked into ${libdir}/pkgconfig/ruby.pc?   That way, if a developer really needs it, they can use PKG_CONFIG_PATH to pick up an alternate one.
----------------------------------------
Bug #6051: Rename ruby-1.9.pc to ruby.pc
https://bugs.ruby-lang.org/issues/6051

Author: Vit Ondruch
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]


Could you please remove the version from ruby-1.9.pc? PKG_CHECK_MODULES provides mechanisms for selecting or constraining versions of the modules, but this mechanism is defeated when the module name includes its version number. "ruby-1.9.pc" should be renamed "ruby.pc" so that, IFF the user needs it, statements like:
    PKG_CHECK_MODULES(RUBY, [ruby >= 1.9],[...]  
can be used.

Originally reported as https://bugzilla.redhat.com/show_bug.cgi?id=789532

Optionally, configuration "--program-prefix" or "--program-suffix" could be used to modify the ruby.pc's filename if more ruby versions are installed on one computer. I can take look into this issue if you prefer.


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