summaryrefslogtreecommitdiff
path: root/doc/install
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-06-30 14:55:03 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-06-30 14:55:03 -0400
commit56aeeb4565dd419c315d370f6e648abfe009a7d3 (patch)
tree224bbf233bc99bd1ac8584dd0ec1b3838de8e920 /doc/install
parentb3aaf980e460c2287fc1ef2b262685b1879e6ed0 (diff)
cabal can now be used to build git-annex.
This is substantially slower than using make, does not build or install documentation, does not run the test suite, and is not particularly recommended, but could be useful to some.
Diffstat (limited to 'doc/install')
-rw-r--r--doc/install/comment_1_d9f7b851567445c7aa7ebbb440781819._comment8
-rw-r--r--doc/install/comment_2_cf0f829536744098d6846500db998b6a._comment17
2 files changed, 0 insertions, 25 deletions
diff --git a/doc/install/comment_1_d9f7b851567445c7aa7ebbb440781819._comment b/doc/install/comment_1_d9f7b851567445c7aa7ebbb440781819._comment
deleted file mode 100644
index 616b3c4dd..000000000
--- a/doc/install/comment_1_d9f7b851567445c7aa7ebbb440781819._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://peter-simons.myopenid.com/"
- ip="84.189.1.247"
- subject="Why isn't this package built with Cabal?"
- date="2011-03-23T11:31:06Z"
- content="""
-It would be a lot easier to compile this package, if it had a Cabal file to describe the build; especially the build-time dependencies. Why isn't Cabal used?
-"""]]
diff --git a/doc/install/comment_2_cf0f829536744098d6846500db998b6a._comment b/doc/install/comment_2_cf0f829536744098d6846500db998b6a._comment
deleted file mode 100644
index 81d5a2c62..000000000
--- a/doc/install/comment_2_cf0f829536744098d6846500db998b6a._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-03-23T15:18:29Z"
- content="""
-Because I haven't learned Cabal yet.
-
-But also because I've had bad experiences with both a) tying a particular program to a particular language's pet build system and then having to add ugliness when I later need to do something in the build that has nothing to do with that language and b) as a user, needing to deal with the pet build systems of languages when I just need to make some small change to the build process that is trivial in a Makefile.
-
-With that said, I do have a configure program written in Haskell, so at least it doesn't use autotools. :)
-
-Update: I did try using cabal, but git-annex includes 3 programs, and they
-all link to a lot of git-annex modules, and cabal wanted to build nearly
-every module 3 times, which was too slow for me and I could not find a way
-around.
-"""]]