Nitro is an efficient, yet simple engine for developing professional Web Applications using the Ruby language (similar to Ruby on rails, but with less hype). Depends on dev-ruby/facets-0.7.2 (Bug 102511, https://bugs.gentoo.org/show_bug.cgi?id=102511) Reproducible: Always Steps to Reproduce: 1. Download ebuilds and put them in your Overlay 2. emerge -av dev-ruby/nitro
Created attachment 65942 [details] nitro-0.22.0.ebuild
Created attachment 65943 [details] glue-0.22.0.ebuild
Created attachment 65944 [details] og-0.22.0.ebuild
Thanks for the report, I will try to add this packages ASAP.
All added to CVS, thanks for the submissions! Some comments: 1. The 3rd line of your header didn't look like the one in /usr/portage/skel.ebuild (you've deleted too much). 2. Looking at the provided Rakefiles helps when looking for dependencies. You actually seem to have done this, as otherwise you wouldn't have noticed the dep on ruby-breakpoint. But you got the dep for facets wrong: nitro itself doesn't depend on this package, but glue does. So if someone only wants to install og (which depends on glue), your deps wouldn't have been correct. Also all the Rakefiles stated that at least ruby-1.8.2 is required. 3. I've added optional support for fastcgi, mysql, postgres and xslt via useflags. The necessary info could be found in INSTALL doc. 4. There's really no need to include the Rubyforge comment in every ebuild that fetches a tarball/gem from there. I know the message appeared in an official ebuild, but I'm trying to get rid from them, as by now everyone should know that Rubyforge's download scheme sucks. In the end this are all rather small issues, but you may want to keep them in mind for future submissions. Thanks once again for this submission, nitro looks really interesting! :)
Ok, next time I'll pay attention to these things. Anyway, I suggest adding some more KEYWORDS to the ebuilds. Since nitro (and rails too for this matter) are only ruby-scripts, it should run on any platform ruby works on (even win32 ;).
But devs only add keywords for arches they can test their packages on. Adding them in because something SHOULD work is pretty bad QA. If you want to get keywords added to Nitro and the related packages, please file bugs requesting them and assign them to the various arch teams (e.g. amd64@gentoo.org). If you own a non-x86 arch, you can also copy the ebuilds to your overlay, keyword them yourself and give them a try. Include this information in your request and it might get looked at faster.
