[Hackage] #523: Config file not automatically generated if symlink-bindir is only item in config

Hackage trac at galois.com
Sun Mar 15 09:05:51 EDT 2009


#523: Config file not automatically generated if symlink-bindir is only item in
config
----------------------------+-----------------------------------------------
  Reporter:  guest          |        Owner:         
      Type:  defect         |       Status:  closed 
  Priority:  normal         |    Milestone:         
 Component:  Cabal library  |      Version:  1.6.0.2
  Severity:  minor          |   Resolution:  fixed  
  Keywords:  config         |   Difficulty:  unknown
Ghcversion:                 |     Platform:         
----------------------------+-----------------------------------------------
Changes (by duncan):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Thanks for the report. I've updated the README. That section now says:

 {{{
 Quickstart on Unix systems
 --------------------------

 As a convenience for users on Unix systems there is a
 `bootstrap.sh` script which will download and install each
 of the dependencies in turn.

     $ ./bootstrap.sh

 It will download and install the above three dependencies.
 The script will install the library packages into
 `$HOME/.cabal/` and the `cabal` program will be installed
 into `$HOME/.cabal/bin/`.

 You then have two choices:

  * put `$HOME/.cabal/bin` on your `$PATH`
  * move the `cabal` program somewhere that is on your `$PATH`

 The next thing to do is to get the latest list of packages with:

     $ cabal update

 This will also create a default config file (if it does not
 already echo exist) at `$HOME/.cabal/config`

 By default cabal will install programs to `$HOME/.cabal/bin`.
 If you do not want to add this directory to your `$PATH` then
 you can change the setting in the config file, for example
 you could use

     symlink-bindir: $HOME/bin

 Quickstart on Windows systems
 -----------------------------

 For Windows users we provide a pre-compiled [cabal.exe]
 program. Just download it and put it somewhere on your
 `%PATH%`, for example
 `C:\Program Files\Haskell\bin`.

 [cabal.exe]:
  http://haskell.org/cabal/release/cabal-install-latest/cabal.exe

 The next thing to do is to get the latest list of packages
 with

     cabal update

 This will also create a default config file (if it does not
 already echo exist) at
 `C:\Documents and Settings\username\Application Data\cabal\config`
 }}}

 The bootstrap script will report something similar:

 {{{
 The 'cabal' program has been installed in $CABAL_BIN/
 You should either add $CABAL_BIN to your PATH
 or copy the cabal program to a directory that is on your PATH.

 The first thing to do is to get the latest list of packages with:
   cabal update
 This will also create a default config file (if it does not already
 exist) at $HOME/.cabal/config

 By default cabal will install programs to $HOME/.cabal/bin
 If you do not want to add this directory to your PATH then you can
 change the setting in the config file, for example you could use:
 symlink-bindir: $HOME/bin
 else
 }}}

 When it prints this for real, it expands the env vars, so it refers to
 real paths not `$CABAL_BIN`.

-- 
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/523#comment:1>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects


More information about the cabal-devel mailing list