# Generated from eav_hashes-1.1.0.gem by gem2rpm -*- rpm-spec -*- %global gem_name eav_hashes Name: rubygem-%{gem_name} Version: 1.1.0 Release: 1%{?dist} Summary: A developer-friendly implementation of the EAV model for Ruby on Rails License: MIT URL: https://github.com/200proof/eav_hashes Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem BuildRequires: ruby(release) BuildRequires: rubygems-devel BuildRequires: ruby # BuildRequires: rubygem(sqlite3) BuildArch: noarch %description eav_hashes allows you to to leverage the power of the EAV database model in the way you would expect to use it: a hash. Unlike other gems which require you to create a special model and/or define which attributes you want to have EAV behavior on (both of which defeat the purpose), all you need to do with eav_hashes is add one line to your model and create a migration. All the heavy lifting is done for you. %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} %license %{gem_instdir}/MIT-LICENSE %{gem_instdir}/init.rb %{gem_libdir} %exclude %{gem_cache} %{gem_spec} %files doc %doc %{gem_docdir} %doc %{gem_instdir}/README.md %{gem_instdir}/Rakefile %{gem_instdir}/spec %changelog * Mon Sep 13 2021 mockbuilder - 1.1.0-1 - Initial package