# Generated from readme-0.1.0.gem by gem2rpm -*- rpm-spec -*-
%global gem_name readme

Name: rubygem-%{gem_name}
Version: 0.1.0
Release: 1%{?dist}
Summary: Extract information from README files
License: BSD-2-Clause
URL: http://rubyworks.github.com/readme
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
# BuildRequires: rubygem(detroit)
# BuildRequires: rubygem(reap)
# BuildRequires: rubygem(mast)
# BuildRequires: rubygem(rubytest)
# BuildRequires: rubygem(citron)
# BuildRequires: rubygem(ae)
# BuildRequires: rubygem(simplecov)
BuildArch: noarch

%description
Ever thought perhaps that all the effect in creating a good README, while
great for your end-userss, did't every do you a hill of beans worth of good
when it came to constructing your project's metadata. Well, hang on to your
nerd glasses! Here comes a gem that does just that!


%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}/


mkdir -p %{buildroot}%{_bindir}
cp -a .%{_bindir}/* \
        %{buildroot}%{_bindir}/

find %{buildroot}%{gem_instdir}/bin -type f | xargs chmod a+x

%check
pushd .%{gem_instdir}
# Run the test suite.
popd

%files
%dir %{gem_instdir}
%{_bindir}/readme
%{gem_instdir}/.ruby
%{gem_instdir}/bin
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}
%doc %{gem_instdir}/HISTORY.md
%doc %{gem_instdir}/README.md

%changelog
* Wed Apr 20 2022 mockbuilder - 0.1.0-1
- Initial package