summaryrefslogtreecommitdiff
path: root/debian/control
blob: 9d7f4a8c5bcb7863870efca42d461bb3aaad4549 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
Source: git-annex
Section: utils
Priority: optional
Build-Depends: 
	debhelper (>= 9),
	ghc (>= 7.4),
	libghc-missingh-dev,
	libghc-hslogger-dev,
	libghc-pcre-light-dev,
	libghc-sha-dev,
	libghc-dataenc-dev,
	libghc-http-dev,
	libghc-utf8-string-dev,
	libghc-hs3-dev (>= 0.5.6),
	libghc-testpack-dev,
	libghc-quickcheck2-dev,
	libghc-monad-control-dev (>= 0.3),
	libghc-lifted-base-dev,
	libghc-json-dev,
	libghc-ifelse-dev,
	libghc-bloomfilter-dev,
	libghc-edit-distance-dev,
	libghc-hinotify-dev [linux-any],
	libghc-stm-dev (>= 2.3),
	libghc-dbus-dev,
	libghc-yesod-dev,
	libghc-yesod-static-dev,
	libghc-yesod-default-dev,
	libghc-case-insensitive-dev,
	libghc-http-types-dev,
	libghc-transformers-dev,
	libghc-wai-dev,
	libghc-wai-logger-dev,
	libghc-warp-dev,
	libghc-blaze-builder-dev,
	libghc-blaze-html-dev,
	libghc-blaze-markup-dev,
	libghc-crypto-api-dev,
	libghc-hamlet-dev,
	libghc-clientsession-dev,
	libghc-network-multicast-dev,
	libghc-network-info-dev,
	ikiwiki,
	perlmagick,
	git,
	uuid,
	rsync,
	openssh-client,
Maintainer: Joey Hess <joeyh@debian.org>
Standards-Version: 3.9.3
Vcs-Git: git://git.kitenet.net/git-annex
Homepage: http://git-annex.branchable.com/

Package: git-annex
Architecture: any
Section: utils
Depends: ${misc:Depends}, ${shlibs:Depends},
	git (>= 1:1.7.7),
	uuid,
	rsync,
	wget | curl,
	openssh-client (>= 1:5.6p1)
Recommends: lsof, libnss-mdns, gnupg
Suggests: graphviz, bup
Description: manage files with git, without checking their contents into git
 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, 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.