# Generated from prong-1.0.0.gem by gem2rpm -*- rpm-spec -*-
%global gem_name prong

Name: rubygem-%{gem_name}
Version: 1.0.0
Release: 1%{?dist}
Summary: Activesupport-like callbacks but upto %20 faster
License: MIT
URL: https://github.com/EhsanYousefi/Prong
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
# BuildRequires: rubygem(rspec)
# BuildRequires: rubygem(pry)
BuildArch: noarch

%description
Prong is almost behave like ActiveSupport::Callbakcs in most of the cases.
It's let you define hooks, add callbacks to them, and conditionally run them
whenever you want. Prong is not just another one, It's faster! It's
independent! Also there is some differences.


%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}
%exclude %{gem_instdir}/.gitignore
%exclude %{gem_instdir}/.travis.yml
%{gem_instdir}/CODE_OF_CONDUCT.md
%license %{gem_instdir}/LICENSE.txt
%{gem_instdir}/bin
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}
%exclude %{gem_instdir}/.rspec
%{gem_instdir}/Gemfile
%doc %{gem_instdir}/README.md
%{gem_instdir}/Rakefile
%{gem_instdir}/prong.gemspec
%{gem_instdir}/test.rb

%changelog
* Tue Apr 19 2022 mockbuilder - 1.0.0-1
- Initial package