Re: Update of Ruby packages

[Takahiro Kambe <taca%back-street.net@localhost>]

In message <00A912F8-3590-4718-8838-CA43B997B838%joyent.com@localhost>
        on Mon, 13 Sep 2010 12:09:12 +0200,
        "Filip Hajny" <filip%joyent.com@localhost> wrote:
> Any reason why the shared object library is symlinked as
> libruby19.so.1.9.1 instead of libruby19.so.1.9.2?
This is semi-FAQ of Ruby 1.9.2.

From Ruby 1.9, Ruby introduce API version. See version.h in source of
ruby 1.9.2:
(http://redmine.ruby-lang.org/repositories/entry/ruby-192/version.h)

----------------------------------------------------------------
#define RUBY_VERSION "1.9.2"
#define RUBY_RELEASE_DATE "2010-08-18"
#define RUBY_PATCHLEVEL 0

#define RUBY_VERSION_MAJOR 1
#define RUBY_VERSION_MINOR 9
#define RUBY_VERSION_TEENY 1
#define RUBY_RELEASE_YEAR 2010
#define RUBY_RELEASE_MONTH 8
#define RUBY_RELEASE_DAY 18
...
----------------------------------------------------------------

RUBY_VERSION defines Ruby's version.  

RUBY_VERSION_MAJOR, RUBY_VERSION_MINOR and RUBY_VERSION_TEENY had
defined Ruby's version but it is now API version from Ruby 1.9.
And it reflects to the version of libruby.so shared library and there
is no difference between API of Ruby 1.9.1 and Ruby 1.9.2.

This isn't pkgsrc specific thing.

> This creates a PLIST conflict.
Why?  PLIST should be generate libruby.so.1.9.1 and if not, something
should be corrected.

-- 
Takahiro Kambe <taca%back-street.net@localhost>