summaryrefslogtreecommitdiff
path: root/Setup.hs
Commit message (Collapse)AuthorAge
* make the standalone OSX app automatically install itself when runGravatar Joey Hess2012-09-26
|
* avoid installing man pages when they do not existGravatar Joey Hess2012-09-01
| | | | | Man pages are shipped prebuilt in cabal tarball, but will not be available when cloning git and running cabal install.
* install autostart file tooGravatar Joey Hess2012-08-01
|
* hook desktop menu file installation into makefile and cabalGravatar Joey Hess2012-08-01
|
* tweakGravatar Joey Hess2012-06-12
|
* Clean up Setup.hs.Gravatar Nathan Collins2012-06-12
| | | | | | | | | Remove post-copy hook 'myPostCopy': it's easy to write one based on 'myPostInst', so just wait until someone complains that it's missing. Remove most comments. Put long type sigs on one line like in the other source files.
* Replace indentation spaces by tabs in Setup.hs.Gravatar Nathan Collins2012-06-10
|
* Combine post install commands in 'postInst' and add 'postCopy' hook.Gravatar Nathan Collins2012-06-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The creation of the 'git-annex-shell' symlink was in 'postInst' hook. I combined it with the man-page installation in a 'postInst' hook and a 'postCopy' hook. I don't understand how to use the `cabal copy` command, but the examples I looked at defined both hooks. Relevant comments from the source: * man-page installation: See http://www.haskell.org/haskellwiki/Cabal/Developer-FAQ#Installing_manpages. Based on pandoc's and lhs2tex's 'Setup.installManpages' and 'postInst' hooks. My understanding: 'postCopy' is run for `cabal copy`, 'postInst' is run for `cabal inst`, and copy is not a generalized install, so you have to write two nearly identical hooks. Summary of hooks: http://www.haskell.org/cabal/release/cabal-latest/doc/API/Cabal/Distribution-Simple-UserHooks.htm-- Other people are also confused: * Bug: 'postCopy' and 'postInst' are confusing: http://hackage.haskell.org/trac/hackage/ticket/718 * A cabal maintainer suggests using 'postCopy' instead of 'postInst', because `cabal install` is `cabal copy` followed by `cabal register`: http://www.haskell.org/pipermail/libraries/2008-March/009416.html Although that sounds desirable, it's not true, as the reply and experiments indicate. * the `cabal copy` command: ???: Not sure how you're supposed to use this. E.g., when I do cabal install --prefix=/tmp/git-annex-install cabal copy --deistdir=/tmp/git-annex-copy I get the copy under /tmp/git-annex-copy/tmp/git-annex-install Also, `cabal install` fails when given a relative --prefix.
* Add note about lhs2tex's man page installation.Gravatar Nathan Collins2012-06-07
|
* WIP: Add man page installation to Setup.hsGravatar Nathan Collins2012-06-06
| | | | | | | | This works with `cabal-dev install .`, but `cabal sdist` does not yet include the man pages (tried adding a `make $(mans)` before `cabal sdist` in `make sdist`, but no luck). XXX: Need to go back and replace spaces with tabs.
* cabal now installs git-annex-shell as a symlink to git-annex.Gravatar Joey Hess2012-04-14
|
* fix use of ConfigureGravatar Joey Hess2012-03-23
|
* Improve detection of inability to check free disk space.Gravatar Joey Hess2012-03-21
| | | | | | | | Don't check if configure indicated checks won't work. This should fix a FTBFS on mipsel, where configure correctly detects the checks won't work, while garbage is returned for disk space info at git-annex runtime. It also means that, when built via cabal, disk space checks are not enabled, unfortunatly.
* Setup.hs: import configureGravatar Joey Hess2012-03-10
| | | | | | | | | | Rather than running make, which runs configure, let Setup.hs just include the configure code. The standalone configure is retained for use by the Makefile. This may work better with cabal-dev, since it avoids the Makefile running ghc, and lets cabal handle all the compiler running, with whatever flags it uses to expose dependencies.
* cabal can now be used to build git-annex.Gravatar Joey Hess2011-06-30
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.