File git-annex.spec of Package git-annex
# cabal2spec-0.25
# https://fedoraproject.org/wiki/Packaging:Haskell
# https://fedoraproject.org/wiki/PackagingDrafts/Haskell
#%%bcond_without docs
Name: git-annex
Version: 4.20130227
Release: 2%{?dist}
Summary: Manage files with git, without checking their contents into git
Group: Productivity/Archiving/Backup
License: GPL-3.0+
# BEGIN cabal2spec
URL: http://hackage.haskell.org/package/%{name}
Source0: http://hackage.haskell.org/packages/archive/%{name}/%{version}/%{name}-%{version}.tar.gz
ExclusiveArch: %{ix86} x86_64 %{ghc_arches}
BuildRequires: ghc-Cabal-devel
BuildRequires: ghc-rpm-macros
# END cabal2spec
BuildRequires: ghc-bloomfilter-devel
BuildRequires: ghc-bytestring-devel
BuildRequires: ghc-containers-devel
BuildRequires: ghc-dataenc-devel
BuildRequires: ghc-directory-devel
BuildRequires: ghc-edit-distance-devel
BuildRequires: ghc-extensible-exceptions-devel
BuildRequires: ghc-filepath-devel
#BuildRequires: ghc-hS3-devel
BuildRequires: ghc-hslogger-devel
BuildRequires: ghc-HTTP-devel
BuildRequires: ghc-IfElse-devel
BuildRequires: ghc-SafeSemaphore-devel
BuildRequires: ghc-uuid-devel
BuildRequires: ghc-json-devel
BuildRequires: ghc-lifted-base-devel
BuildRequires: ghc-MissingH-devel
BuildRequires: ghc-monad-control-devel
BuildRequires: ghc-mtl-devel
BuildRequires: ghc-network-devel
BuildRequires: ghc-old-locale-devel
BuildRequires: ghc-pcre-light-devel
BuildRequires: ghc-process-devel
BuildRequires: ghc-QuickCheck-devel
BuildRequires: ghc-SHA-devel
BuildRequires: ghc-text-devel
BuildRequires: ghc-time-devel
BuildRequires: ghc-transformers-base-devel
BuildRequires: ghc-unix-devel
BuildRequires: ghc-utf8-string-devel
BuildRequires: git
#%%if %%{with docs}
#BuildRequires: ikiwiki
#BuildRequires: perl(Image::Magick)
#%%endif
Requires: git
%description
git-annex allows managing files with git, without checking the file contents
into git. While that may seem paradoxical, it is useful when dealing with files
larger than git can currently easily handle, whether due to limitations in
memory, checksumming time, or disk space.
Even without file content tracking, being able to manage files with git, move
files around and delete files with versioned directory trees, and use branches
and distributed clones, are all very handy reasons to use git. And annexed
files can co-exist in the same git repository with regularly versioned files,
which is convenient for maintaining documents, Makefiles, etc that are
associated with annexed files but that benefit from full revision control.
When a file is annexed, its content is moved into a key-value store, and a
symlink is made that points to the content. These symlinks are checked into git
and versioned like regular files. You can move them around, delete them, and so
on. Pushing to another git repository will make git-annex there aware of the
annexed file, and it can be used to retrieve its content from the key-value
store.
%prep
%setup -q
%build
%ghc_bin_build
%install
%ghc_bin_install
ln -s %{name} %{buildroot}%{_bindir}/%{name}-shell
mkdir -p %{buildroot}%{_mandir}/man1
install -m 0644 git-annex.1 %{buildroot}%{_mandir}/man1
install -m 0644 git-annex-shell.1 %{buildroot}%{_mandir}/man1
%files
%doc COPYRIGHT
%attr(755,root,root) %{_bindir}/%{name}
%attr(755,root,root) %{_bindir}/%{name}-shell
%attr(644,root,root) %{_mandir}/man1/git-annex.1*
%attr(644,root,root) %{_mandir}/man1/git-annex-shell.1*
%changelog
* Sun Mar 3 2013 nurio <buildservice@nurio.at> 4.20130227
- modified spec file to fix lint warnings
* Sun Mar 3 2013 Fedora Haskell SIG <haskell-devel@lists.fedoraproject.org>
- spec file template generated by cabal2spec-0.25.5