# Generated from patir-0.9.0.gem by gem2rpm -*- rpm-spec -*- %global gem_name patir Name: rubygem-%{gem_name} Version: 0.9.0 Release: 1%{?dist} Summary: patir (Project Automation Tools in Ruby) provides libraries for use in project automation tools License: MIT URL: http://github.com/damphyr/patir Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem BuildRequires: ruby(release) BuildRequires: rubygems-devel BuildRequires: ruby # BuildRequires: rubygem(hoe) >= 3.16 # BuildRequires: rubygem(hoe) < 4 BuildArch: noarch %description [patir](http://patir.rubyforge.org) provides code to enable project automation tasks: * A logging format for ruby's built-in Logger * A command abstraction with a platform independent implementation for running shell commands and ruby code * Command sequences using the same command abstraction as single commands. * Configuration format for configuration files written in ruby. ## Why? We've been using the same things again and again and can't be bothered to code it anew every time. The command abstraction has been used the most, the Logger defaults and formatting the least. %package doc Summary: Documentation for %{name} Requires: %{name} = %{version}-%{release} BuildArch: noarch %description doc Documentation for %{name}. %prep %setup -q -n %{gem_name}-%{version} %build # Create the gem as gem install only works on a gem file gem build ../%{gem_name}-%{version}.gemspec # %%gem_install compiles any C extensions and installs the gem into ./%%gem_dir # by default, so that we can move it into the buildroot in %%install %gem_install %install mkdir -p %{buildroot}%{gem_dir} cp -a .%{gem_dir}/* \ %{buildroot}%{gem_dir}/ %check pushd .%{gem_instdir} # Run the test suite. popd %files %dir %{gem_instdir} %{gem_instdir}/Manifest.txt %{gem_libdir} %exclude %{gem_cache} %{gem_spec} %files doc %doc %{gem_docdir} %doc %{gem_instdir}/History.txt %doc %{gem_instdir}/README.txt %{gem_instdir}/Rakefile %{gem_instdir}/test %changelog * Tue Sep 14 2021 mockbuilder - 0.9.0-1 - Initial package