Project

General

Profile

Actions

Backport #6051

closed

Rename ruby-1.9.pc to ruby.pc

Added by vo.x (Vit Ondruch) about 12 years ago. Updated almost 12 years ago.

Status:
Closed
Assignee:
-
[ruby-core:42764]

Description

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.


Related issues 1 (0 open1 closed)

Related to Backport193 - Backport #6052: please add vendorarchdir and vendorlibdir to ruby.pcClosed02/21/2012Actions

Updated by ellson (John Ellson) about 12 years ago

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.

Updated by shevegen (Robert A. Heiler) about 12 years ago

I support ruby.pc

It is the simplest solution. I am not a fan of versioned .pc files at all (when the versioning is part of the name).

It is not even consistent - there would not be a ruby-1.8.pc nor a ruby 1.8.7.pc nor a ruby 1.9.4.pc file.

.pc files already contain the version of the program, so it is useless to put the name as filename as well.

Also, developers who want to use multiple versions can also compile into versioned directories.

I use this to compile into

/Programs/Ruby/VERSION_HERE

So I have:

/Programs/Ruby/1.9.3
/Programs/Ruby/1.8.7p358

And so on, with subdirs like lib/ include/ bin/ there. And my ruby scripts
switch, a bit similar to how RVM does it, between these versions as I need
it.

Updated by ellson (John Ellson) about 12 years ago

Has this issue slipped through the cracks? I was really hoping that a clean ruby.pc would hit Fedora distributions before the next graphviz release.

Updated by nobu (Nobuyoshi Nakada) about 12 years ago

I see many versioned pc files in pkgconfig directories, why are they?

Actions #5

Updated by nobu (Nobuyoshi Nakada) about 12 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r34880.
Vit, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


  • configure.in (ruby_pc): make configurable. [Bug #6051]

Updated by vo.x (Vit Ondruch) almost 12 years ago

Would you mind to backport this into 1.9.3? Thank you.

Actions #7

Updated by kosaki (Motohiro KOSAKI) almost 12 years ago

  • Tracker changed from Bug to Backport
  • Project changed from Ruby master to Backport193
  • Status changed from Closed to Open
Actions #8

Updated by naruse (Yui NARUSE) almost 12 years ago

  • Status changed from Open to Closed

This issue was solved with changeset r36562.
Vit, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


merge revision(s) 34880:

* configure.in (ruby_pc): make configurable.  [Bug #6051]
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0Like0