Ruby Reports (ruport) is a very popular tool set, compatible with all of the popular Ruby tools, like Rails. I have not attempted an ebuild, but it looks straightforward, given that it's available as a "gem" and most of its dependencies are already in Portage. I have it running on my Gentoo boxes as a gem.
Created attachment 143228 [details] Ebuild for Ruport Tested only with Ruby 1.8 If 'pdf' use flag is set it will pull in dev-ruby/pdf-writer-1.1.7, which in turn will pull in dev-ruby/color-1.4.0 and dev-ruby/archive-tar-minitar-0.5.1 Currently, these three ebuilds are keyworded ~amd64 only, so you will have to modify in your overlay for now on other arches. ~x86 Keyword request is bug #209691 I attempted an ebuild for ruport-util as well, but it depends on packages not in portage.
(In reply to comment #1) > Created an attachment (id=143228) [edit] > Ebuild for Ruport > > Tested only with Ruby 1.8 > > If 'pdf' use flag is set it will pull in dev-ruby/pdf-writer-1.1.7, which in > turn will pull in dev-ruby/color-1.4.0 and dev-ruby/archive-tar-minitar-0.5.1 > > Currently, these three ebuilds are keyworded ~amd64 only, so you will have to > modify in your overlay for now on other arches. ~x86 Keyword request is bug > #209691 > > I attempted an ebuild for ruport-util as well, but it depends on packages not > in portage. > 1. Very little of the "traditional" Ruby infrastructure (Rails, rspec, etc.) works with Ruby 1.9 yet, and nearly all of it works with jRuby. :) 2. $ gem dependency ruport Gem ruport-1.4.0 fastercsv (>= 1.1.0) pdf-writer (= 1.1.7) Gem ruport-util-0.12.0 ruport (>= 1.2.3) mailfactory (>= 1.2.3) rubyzip (>= 0.9.1) I can't imagine "rubyzip" or "mailfactory" being difficult to wrap in an ebuild -- they both appear to be pure Ruby.
Created attachment 166353 [details] version bump
Created attachment 166355 [details] ruport utilities
Created attachment 166357 [details] ruport-util requires mailfactory Need to be double checked.
Created attachment 166359 [details] module for ruport to regerate openoffice documents
You can add ~amd64.
ruport-1.6.1 seems to require fastercsv 1.2.3. This was in line with what I had on my ~amd64 system, but not my x86 machine.
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. 1.6.3 December 12, 2009 seems to be the recent version according to rubygems.
(In reply to Manuel Rüger from comment #9) > 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. > > 1.6.3 December 12, 2009 seems to be the recent version according to > rubygems. is this a joke? Yes, there is still interest. It would be good to have some reporting software in the portage. I had to care around ruports ebuilds and host them locally everytime. https://github.com/ruport/ruport/commits/master The latest commit was on Jan 30, 2013. There are also alternatives, such as https://github.com/sandrods/odf-report
(In reply to Anton Bolshakov from comment #10) > (In reply to Manuel Rüger from comment #9) > > 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. > > > > 1.6.3 December 12, 2009 seems to be the recent version according to > > rubygems. > > is this a joke? Yes, there is still interest. It would be good to have some > reporting software in the portage. > No it isn't. I just want to see if there are people interested in it. > I had to care around ruports ebuilds and host them locally everytime. > https://github.com/ruport/ruport/commits/master > The latest commit was on Jan 30, 2013. > > There are also alternatives, such as https://github.com/sandrods/odf-report You can maintain it in the tree via proxy-maintainers. Just add a polished ebuild here (please with working tests and satisfied dependencies) and I'll get it into the tree.
