summaryrefslogtreecommitdiff
path: root/dev-vcs/git-annex/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2020-08-25 10:45:55 +0100
committerV3n3RiX <venerix@redcorelinux.org>2020-08-25 10:45:55 +0100
commit3cf7c3ef441822c889356fd1812ebf2944a59851 (patch)
treec513fe68548b40365c1c2ebfe35c58ad431cdd77 /dev-vcs/git-annex/metadata.xml
parent05b8b0e0af1d72e51a3ee61522941bf7605cd01c (diff)
gentoo resync : 25.08.2020
Diffstat (limited to 'dev-vcs/git-annex/metadata.xml')
-rw-r--r--dev-vcs/git-annex/metadata.xml47
1 files changed, 28 insertions, 19 deletions
diff --git a/dev-vcs/git-annex/metadata.xml b/dev-vcs/git-annex/metadata.xml
index 556f1c584b7f..58517e95d4ad 100644
--- a/dev-vcs/git-annex/metadata.xml
+++ b/dev-vcs/git-annex/metadata.xml
@@ -5,29 +5,38 @@
<email>haskell@gentoo.org</email>
<name>Gentoo Haskell</name>
</maintainer>
- <longdescription>
- 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.
- </longdescription>
<use>
<flag name="assistant">Enable git-annex assistant and watch command</flag>
<flag name="benchmark">Enable benchmarking</flag>
- <flag name="concurrentoutput">Use concurrent-output library (experimental)</flag>
- <flag name="network-uri">Get Network.URI from the network-uri package.</flag>
- <flag name="pairing">Enable pairing of git annex repositories</flag>
- <flag name="s3">Enable Amazon S3 remote</flag>
+ <flag name="dbus">Enable dbus support</flag>
+ <flag name="debuglocks">Debug location of MVar/STM deadlocks</flag>
+ <flag name="gitlfs">Build with git-lfs library (rather than vendored copy)</flag>
+ <flag name="httpclientrestricted">Build with http-client-restricted library (rather than vendored copy)</flag>
+ <flag name="magicmime">Use libmagic to determine file MIME types</flag>
+ <flag name="networkbsd">Build with network-3.0 which split out network-bsd</flag>
+ <flag name="pairing">Enable pairing</flag>
+ <flag name="s3">Enable S3 support</flag>
<flag name="torrentparser">Use haskell torrent library to parse torrent files</flag>
<flag name="webapp">Enable git-annex webapp</flag>
- <flag name="webdav">Enable webdav remote</flag>
+ <flag name="webdav">Enable WebDAV support</flag>
</use>
+ <longdescription>
+ 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.
+
+ It can store large files in many places, from local hard drives, to a
+ large number of cloud storage services, including S3, WebDAV,
+ and rsync, with a dozen cloud storage providers usable via plugins.
+ Files can be stored encrypted with gpg, so that the cloud storage
+ provider cannot see your data. git-annex keeps track of where each file
+ is stored, so it knows how many copies are available, and has many
+ facilities to ensure your data is preserved.
+
+ git-annex can also be used to keep a folder in sync between computers,
+ noticing when files are changed, and automatically committing them
+ to git and transferring them to other computers. The git-annex webapp
+ makes it easy to set up and use git-annex this way.
+ </longdescription>
</pkgmetadata>