I don't think it actually requires ruby-libs, but the way I figure, they're going to need the ruby stdlib if they're going to actually install most gems. Better to set up the expectation in advance, IMO.Matt Rose wrote:requires: ruby >= 1.8.5, ruby-libs >= 1.8.5Are you sure about that? I only have Requires: ruby(abi) = 1.8 in my spec (which is for 1.1.1 though)
Because I forgot the syntax for BuildRequiresSource0: %{name}-%{version}.tgz License: GPLI think naming both licenses is correct here: License: Ruby License/GPLBuildPreReq: ruby >= 1.8.5, ruby-libs >= 1.8.5Hmmm. Why PreReq? I have BuildRequires: ruby, ruby-irb, ruby-rdoc in my spec.
%description Ruby GemsRubyGems is the Ruby standard for publishing and managing third party libraries. Yours is a tad short :)cd $RPM_BUILD_ROOT rm -rf %{buildroot}Hmmm. Either or, I think. Not both in one spec file :)
we could put them up on github or I could host a publically available subver repo for ruby gem rpms, or something. It would be nice to have a central repo for exactly this kind of stuff. I wonder how hard it would be to do a gem2rpm script, like perl has with cpan2rpm.I also have a wad of rubygems which are packaged and should be published somewhere (like a complete rails 2.1 environment, mod_passenger and other stuff). Cheers, Ralph