# Generated from erb-file_out-0.1.2.gem by gem2rpm -*- rpm-spec -*-
%global gem_name erb-file_out

Name: rubygem-%{gem_name}
Version: 0.1.2
Release: 1%{?dist}
Summary: Store ERB result on disc instead of in memory
License: MIT
URL: https://github.com/matchbookmac/erb-file_out
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
# BuildRequires: rubygem(rspec)
# BuildRequires: rubygem(rubocop)
# BuildRequires: rubygem(dotenv)
# BuildRequires: rubygem(simplecov)
# BuildRequires: rubygem(codeclimate-test-reporter)
BuildArch: noarch

%description
By default, ERB compiles a script from the template and stores the result as a
string in memory.
This is not great when dealing with templates that could end up being very
large after
rendering. ERB::FileOut provides a way to write the result of a template to
disk instead of
storing it in memory.


%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}
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}


%changelog
* Mon Sep 13 2021 mockbuilder - 0.1.2-1
- Initial package