# Generated from simple_units-0.0.0.gem by gem2rpm -*- rpm-spec -*-
%global gem_name simple_units

Name: rubygem-%{gem_name}
Version: 0.0.0
Release: 1%{?dist}
Summary: Simple units implementation. Similar to ruby-units except with a lot less features and zero collisons with rails
License: MIT
URL: http://github.com/foxnewsnetwork/simple_units
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
# BuildRequires: rubygem(rspec) >= 2.8.0
# BuildRequires: rubygem(jeweler) >= 1.8.4
# BuildRequires: rubygem(simplecov)
BuildArch: noarch

%description
Sure, ruby is dynamic and that is one of its greatest strength. Object
polymorphisms, duck typing, and the like is great in ruby, there is a time and
place for everything. Sometimes, it just makes more sense to be strongly
typed.


%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}
# rspec spec
popd

%files
%dir %{gem_instdir}
%license %{gem_instdir}/LICENSE.txt
%{gem_instdir}/VERSION
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}
%doc %{gem_instdir}/.document
%exclude %{gem_instdir}/.rspec
%{gem_instdir}/Gemfile
%{gem_instdir}/Gemfile.lock
%doc %{gem_instdir}/README.rdoc
%{gem_instdir}/Rakefile
%{gem_instdir}/spec

%changelog
* Wed Sep 15 2021 mockbuilder - 0.0.0-1
- Initial package