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

Name: rubygem-%{gem_name}
Version: 1.0.0
Release: 1%{?dist}
Summary: Pragmatic Studio's Ruby Programming's Workbook App
License: MIT
URL: https://github.com/waihon/prag_studio_game
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby >= 1.9
# BuildRequires: rubygem(rspec) >= 3.5
# BuildRequires: rubygem(rspec) < 4
BuildArch: noarch

%description
Studio Game is a Ruby program developed based on Pragmatic Studio' Ruby
Programming hands-on video course, and distributed as a Ruby gem.
This program has been developed using all the strengths of Ruby including the
following.
Ruby Programming Environment
* Installing Ruby on your favorite operating system (free exercise)
* Running Ruby using the interactive Ruby shell (irb) and writing Ruby program
files
* Using Ruby's documentation system to get help
* Installing external Ruby libraries using RubyGems
* Troubleshooting common problems
Ruby Language Constructs
* Expressions and variables
* Numbers, string, and symbols (free video & exercise)
* Loops and conditional expressions
* Arrays and hashes (free video & exercise on hashes)
* Classes, modules, and structs
Object-Oriented Programming
* Using built-in Ruby classes
* Defining your own classes with state and behavior (free video & exercise)
* Creating unique objects
* Telling objects what to do by calling methods
* Modeling class-level inheritance relationships
* Sharing code with mixins
Object-Oriented Design Principles
* Encapsulation
* Separation of concerns
* Polymorphism
* Don't Repeat Yourself
* Tell, Don't Ask
Blocks and Iterators
* Calling built-in methods that take blocks
* Writing your own methods that yield to blocks
* Implementing custom iterators
* Effectively using blocks in your programs
Organizing Ruby Code
* Creating a Ruby project structure
* Separating source files for easier reuse and testing
* Namespacing to avoid naming clashes
* Input/Output
* Reading data from files
* Writing data to files
* Creating an interactive console prompt
* Handling command-line input
Unit Testing
* Writing and running unit tests with RSpec
* Test-driven development and the red-green-refactor cycle
* Stubbing methods to control tests
* Refactoring code, safely!
Distribution
* Conforming to RubyGems conventions
* Writing a GemSpec
* Building a RubyGem
* Publishing a RubyGem to a public server
Ruby Programming Idioms.


%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}
# rspec spec
popd

%files
%dir %{gem_instdir}
%{_bindir}/studio_game
%license %{gem_instdir}/LICENSE
%{gem_instdir}/bin
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}
%doc %{gem_instdir}/README
%{gem_instdir}/spec

%changelog
* Tue Sep 14 2021 mockbuilder - 1.0.0-1
- Initial package