mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

responses

Browse source
This commit is contained in:
Joey Hess 2018-12-09 11:31:43 -04:00
parent 41b9d77201
commit 7d5b56d99c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 55 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/forum/android_installation/comment_1_8908256ecd48d7b5207799aa02102d87._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-12-09T15:25:24Z"
content="""
The installer is running the command `uname -m` to find out what kind of
processor your Android device has. It doesn't recognize "armv81"
What you can try is to open the git-annex-install
script in a text editor, and add a case under `uname -m` for
"armv81". My guess is that this would work:
armv81) arch=arm64 ;;
Or maybe this:
armv81) arch=arm ;;
"""]]

17
doc/forum/conda-forge_build_problem/comment_1_22e01f5f110593796b539fc7630ccb3c._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-12-09T15:15:36Z"
content="""
The way that stack works is the "resolver" value in stack.yaml
points to a particular version of ghc and libraries that work with it.
I don't think that stack allows overriding the version of ghc. What you can
do is go to <http://stackage.org/> and find a snapshot that includes the
ghc version you have available, and edit stack.yaml's "resolver" to use
that. You may also need to pass --system-ghc to stack to make it use your
installed ghc rather than trying to download it.
Building with cabal, while more error prone, is another way to use whatever
version of ghc you have installed already.
"""]]

20
doc/forum/export_single_file/comment_3_0761201bf68e1086d263776eb953c1e1._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2018-12-09T15:22:09Z"
content="""
`git annex export` only exports trees, but you can easily make a tree
containing only a single file, and then export that.
For example:
mkdir exporttree
cp tests/tests1.mov exporttree
git annex add exporttree
git commit -m 'created export tree'
git annex export master:exporttree --to public
If you don't want to commit that you can switch to a temporary branch
and build the tree there. Or there are plenty of lower-level git commands
to build trees.
"""]]