# Generated from rabbit-slide-kou-rubykaigi-takeout-2020-2020.9.4.3.gem by gem2rpm -*- rpm-spec -*-
%global gem_name rabbit-slide-kou-rubykaigi-takeout-2020

Name: rubygem-%{gem_name}
Version: 2020.9.4.3
Release: 1%{?dist}
Summary: Goodbye fat gem
License: CC-BY-SA-4.0
URL: https://slide.rabbit-shocker.org/authors/kou/rubykaigi-takeout-2020/
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
BuildArch: noarch

%description
Fat gem mechanism is useful to install extension library without any
compiler. Fat gem mechanism is especially helpful for Windows rubyists
because Windows rubyists don't have compiler. But there are some
downsides. For example, fat gem users can't use Ruby 2.7 (the latest
Ruby) until fat gem developers release a new gem for Ruby 2.7. As of
2020, pros of fat gem mechanism is decreasing and cons of it is
increasing. This talk describes the details of pros and cons of it then
says thanks and goodbye to fat gem.


%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}/.rabbit
%{gem_instdir}/config.yaml
%{gem_instdir}/goodbye-fat-gem.rab
%{gem_instdir}/images
%{gem_instdir}/pdf
%{gem_instdir}/theme.rb
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}
%doc %{gem_instdir}/README.rd
%{gem_instdir}/Rakefile

%changelog
* Tue Aug 24 2021 mockbuilder - 2020.9.4.3-1
- Initial package