[Hackage] #289: symlink binaries into ~/bin
Hackage
trac at galois.com
Sun Feb 1 16:00:26 EST 2009
#289: symlink binaries into ~/bin
---------------------------------+------------------------------------------
Reporter: duncan | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: cabal-install-0.6
Component: cabal-install tool | Version:
Severity: normal | Resolution:
Keywords: | Difficulty: easy (<4 hours)
Ghcversion: 6.8.2 | Platform:
---------------------------------+------------------------------------------
Comment (by guest):
From alson [at] alsonkemp [dot] com:
My issues with the current behavior are that it doesn't act as I would
expect it to act (~/bin) and I don't really want to figure out to make it
work correctly. While I can put on my hacker hat and solve the issue
locally, the just-the-defaults-please user in me still isn't happy.
A possible solution is to force the user to choose the location. This
would:
* Be quick and would be done once;
* Make the situation perfectly clear;
* Would alert the user to the future location of binaries.
Something like if "bindir" isn't set in ~/.cabal/config, then force the
user to set it _during the build_:
{{{
I need to install some binaries to complete this package,
but I'm not sure where you'd like me to place them. Common
locations are:
Windows: %APP_DATA%\GHC\bin
Linux, MacOS, Unix: ~/bin
This setting will be stored in the "bindir" setting of ~/.cabal/config.
Where should I put them : _________________________________
}}}
If it's difficult to interrupt the build process for interaction with the
user, then, since rrrors currently get a bit lost in all of the cabal
install text, scream at them to set bindir:
{{{
===========================================================
===========================================================
I need to install some binaries to complete this package,
but I'm not sure where you'd like me to place them. Common
locations are:
Windows: %APP_DATA%\GHC\bin
Linux, MacOS, Unix: ~/bin
*** Please set the "bindir" setting of ~/.cabal/config. ***
*** Then re-run "cabal install". ***
===========================================================
===========================================================
}}}
Either of these would make me happy since I prefer loud-and-clear to
silent-and-unexpected...
--
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/289#comment:16>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects
More information about the cabal-devel
mailing list