[ruby-core:42764] [ruby-trunk - Bug #6051][Open] Rename ruby-1.9.pc to ruby.pc

1 view
Skip to first unread message

Vit Ondruch

unread,
Feb 20, 2012, 10:45:09 AM2/20/12
to ruby...@ruby-lang.org

Issue #6051 has been reported by Vit Ondruch.

----------------------------------------
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/

John Ellson

unread,
Feb 20, 2012, 11:46:35 AM2/20/12
to ruby...@ruby-lang.org

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.

markus heiler

unread,
Feb 21, 2012, 4:03:11 PM2/21/12
to ruby...@ruby-lang.org

Issue #6051 has been updated by markus heiler.


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.

John Ellson

unread,
Mar 2, 2012, 2:01:46 PM3/2/12
to ruby...@ruby-lang.org

Issue #6051 has been updated by John Ellson.


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.

Nobuyoshi Nakada

unread,
Mar 2, 2012, 3:58:18 PM3/2/12
to ruby...@ruby-lang.org

Issue #6051 has been updated by Nobuyoshi Nakada.


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

vo.x (Vit Ondruch)

unread,
Jun 29, 2012, 9:50:00 AM6/29/12
to ruby...@ruby-lang.org

Issue #6051 has been updated by vo.x (Vit Ondruch).


Would you mind to backport this into 1.9.3? Thank you.
----------------------------------------
Bug #6051: Rename ruby-1.9.pc to ruby.pc
https://bugs.ruby-lang.org/issues/6051#change-27562

Author: vo.x (Vit Ondruch)
Status: Closed
Reply all
Reply to author
Forward
0 new messages