or Create a profile
24 May, 2011 09:28 PM
shows an incorrect version in title: "libnotify 0.5.1"
The correct version be "0.5.3".
There is also an issue from an user on github which is might
related to the problem described above:
(I have no issues installing libnotify)
BTW, since 0.5.2 I'm pushing 3 platform-specific versions of
libnotify (ruby, jruby and rubinius).
Since then libnotify's dashboard displays incorrect stats in "for
Am I doing something wrong?
2 Posted by Luis Lavena on 24 May, 2011 09:38 PM
RubyGems.org takes the latest version stable that has
ruby as platform. In the case of libnotify, none of
the 0.5.3 gems have a ruby platform, except for
The source code of RubyGems is here:
And the lines that are affecting you are the following ones:
Since your case is one of the few, perhaps you can checkout the
application and provide a patch for it to take either the latest
ruby or any platform present.
Please let me know if that help you somehow.
3 Posted by Peter Suschlik on 24 May, 2011 10:19 PM
thanks for your quick response and your hint about the
ruby as platform.
Instead of using Gem::Platform::CURRENT I'm using
Gem::Platform::RUBY in gemspec now, which seem to
solve the "title issue":
I'm still not sure how to use platform correctly and couldn't
find good (and simple) examples for a multi platform gem.
Do you have any hints for me?
(If not, just close that issue ;))
Again, thanks for your help!
4 Posted by Luis Lavena on 24 May, 2011 10:31 PM
Happy to hear that worked.
Most of the times CURRENT should be used to
indicate a native extension needs to be compiled
I checked that libnotify depends on ffi, which makes that
particular dependency useless.
Most of the times gems should be simple ruby as you
don't contain there platform or engine specific code (being Windows
a platform or Java/Rubinius a Ruby engine)
I see there is also a Java gem, what differences it from the
others? is not using FFI or is using a pure-java library
What about the Rubinius one? it does contain any Rubinius
specific code that is not contained in the other gems?
If the answers to above questions is no, then there is no need
to have a Java and a Rubinius version.
I believe JRuby already includes a shim 'ffi' gem, so that could
solve the ffi dependency.
By that means the java version of the gem is not required
As for Rubinius, I don't remember, so I think it does which you
should keep the rubinius gem without the ffi dependency on it.
This is good candidate content for the new guides:
5 Posted by Peter Suschlik on 24 May, 2011 11:23 PM
Many answers & questions :)
Rubinius has its own ffi and does not work with gem
Therefore I have to exclude ffi dependency for Rubinius.
I remember I had issues the ffi gem for Java which I can't
reproduce right now.
It just works, so I'll remove the Java version ;)
Ok, that's it. You can close this issue now :D
Peter Suschlik closed this discussion
on 25 May, 2011 06:09 AM.
Comments are currently closed for this discussion.
You can start a new one.
2 people watching.
No more actions from RubyGems.org or the discussion starter are required.
This discussion is private.
Only you and RubyGems.org support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.