Hello. I have written an ebuild script for wmainfo-rb, which is a pure Ruby library for accessing metadata from WMA/WMV or other files with an ASF header. Its main purpose would be to grab 'id3' like data from Windows Media files, though other data can also be accessed. The script grabs and installs the package via gems, and comes with rdoc documentation if used with the 'doc' USE flag. I am not sure whether it is more appropriate in media-libs or dev-ruby. I have it in media-libs in my local portage overlay.
Created attachment 96370 [details] wmainfo-rb-0.3.ebuild (new package)
Hello. I'd say dev-ruby since it's a library used when developing with Ruby. If you are interested in improving your ebuild, you may want to read the section about ebuild writing: http://devmanual.gentoo.org/ebuild-writing/index.html Regards.
Thanks for the link Aggelos, this is much more comprehensive then the ebuild HOWTO. As for improving the ebuild, is there something wrong with it? I have basically just modelled it from an existing ebuild for a Ruby lib that is similar to mine. I tested in overlay and it seems just fine... I am more than willing to improve it if I new what was wrong/substandard with it...
Hello. Yeah, as I see it, the ebuild should work fine. It's just that there are other aspects of it that can be improved. For example, KEYWORDS should contain the architectures, as ~arch, under which you have actually tested the ebuild. USE_RUBY should be "any" if you've tested and seen that the library works with Ruby 1.6.*, Ruby 1.8.* and Ruby 1.9.* without any issues. You could also have RDEPEND have a value of the version of Ruby that you have tested the library under; e.g. ">=dev-lang/ruby-1.8.4" would be a good candidate for up-to-date systems. Hope this helps.
Created attachment 97597 [details] Update to ebuild Just some minor fixes, changed USE_RUBY to "ruby18" and changed ARCH to "~x86" as that's all I have tested on.
This package has been tested quite successfully with (on-coming) g-gem, an ebuild generator for gems. Once I release g-gem, I will reconsider this package and add it if g-gem can't handle it.
Reassigning back to herd since Nguyen has retired as a Gentoo developer (#49680).
this ebuild can be updated to 0.5, though it is too buggy to use, but then there is v0.4 which works well.
Vytautas Jakutis, I wasn't aware version 0.5 had issues, no one has sent me a bug report. Would you consider sending a report on these issues (the library itself, not the ebuild) directly to me, as I am the upstream developer. Thanks!
(In reply to comment #9) > Vytautas Jakutis, > > I wasn't aware version 0.5 had issues, no one has sent me a bug report. Would > you consider sending a report on these issues (the library itself, not the > ebuild) directly to me, as I am the upstream developer. Thanks! > Ok, just sent you an email with details
Assigning this to maintainer-wanted since it is now yet in the tree. Note that we are trying to move away from the old ruby and gems eclasses. For a version bump you might want to look at ruby-fakegem instead.
Is there still any interest to get this into the tree? Please reply, otherwise the bug will be marked as WONTFIX in 30 days from now. 0.6 June 7, 2009 seems to be the recent version according to rubygems.
Hello. Original upstream dev here. I for one would still like to see this added, it is a useful library for what it does. The project was hosted on Rubyforge which has since been shutdown. So the project is currently homeless, however, I have found someone who will take over official development of the project (he forked it and his latest version is 0.8 released in 2012), and he is intending to move it to a github repository to once again have the source, documentation, and a bug tracker publicly available. I should also mention that both me and the new official maintainer agree the library is essentially 'complete', in the sense it has all the functionality that was originally intended. I will write an updated ebuild script once the new home for the project is settled, and if at that time there is no will from the gentoo devs to add it to the tree, I will try to find an overlay for it, or otherwise make the ebuild accessible.
