%global gem_name git-up 
%global git_bindir %{_libexecdir}/git-core

Name: rubygem-%{gem_name}
Version: 0.5.12
Release: 1%{?dist}
Summary: git command to fetch and rebase all branches

Group: Development/Languages
License: MIT
URL: http://github.com/aanand/%{gem_name}
Source1: http://rubygems.org/downloads/%{gem_name}-%{version}.gem
Patch1: 0001-bin-use-system-ruby.patch

BuildArch: noarch
BuildRequires: rubygems-devel
%if %{fedora} >= 19
Requires: ruby(release)
%endif
Requires: rubygems
Requires: rubygem-colored >= 1.2, rubygem-grit
Requires: git

%description

Regular 'git pull' has two problems:

* It merges upstream changes by default, when it's really more polite to
  rebase over them, unless your collaborators enjoy a commit graph that looks
  like bedhead.

* It only updates the branch you're currently on, which means git push will
  shout at you for being behind on branches you don't particularly care about
  right now.

Solve them once and for all.


%package doc
Summary: Documentation for %{name}
Group: Documentation
Requires: %{name} = %{version}-%{release}
BuildArch: noarch

%description doc
Documentation for %{name}


%prep
gem unpack %{SOURCE1}
%setup -q -D -T -n %{gem_name}-%{version}
%patch1 -p1
gem spec %{SOURCE1} -l --ruby > %{gem_name}.gemspec


%build
gem build %{gem_name}.gemspec
%gem_install


%install
mkdir -p %{buildroot}%{gem_dir}
cp -a ./%{gem_dir}/* %{buildroot}%{gem_dir}/

mkdir -p %{buildroot}%{git_bindir}/git-core
ln -s ../../..%{gem_instdir}/bin/git-up %{buildroot}%{git_bindir}/git-up


%files
%dir %{gem_instdir}
%doc %{gem_instdir}/LICENSE
%doc %{gem_instdir}/README.md
%{gem_libdir}
%{gem_cache}
%{gem_spec}
%{gem_instdir}/bin
%{gem_instdir}/man
%{git_bindir}/git-up


%files doc
%doc %{gem_docdir}


%changelog
* Wed Sep 11 2013 Jan Vcelak <jvcelak@fedoraproject.org> 0.5.12-1
- update to newer version

* Sun Mar 31 2013 Jan Vcelak <jvcelak@fedoraproject.org> 0.5.8-1
- initial package