[Hackage] #312: Multiple architectures under .cabal/
#312: Multiple architectures under .cabal/ ------------------------------+--------------------------------------------- Reporter: larsv | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: minor | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.2 Platform: | ------------------------------+--------------------------------------------- Currently, the path in the home directory which cabal-install puts installed packages in does not contain the architecture in any way. This makes things bothersome for people who has the same ${HOME} on several different architectures. The proposed solution in #haskell is to "add ${arch} as a path template". -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/312 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#312: Allow ${arch} var in install paths ----------------------------+----------------------------------------------- Reporter: larsv | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Cabal-1.4 Component: Cabal library | Version: 1.2.3.0 Severity: minor | Resolution: Keywords: | Difficulty: very easy (<1 hour) Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Changes (by duncan): * difficulty: easy (<4 hours) => very easy (<1 hour) * summary: Multiple architectures under .cabal/ => Allow ${arch} var in install paths * milestone: => Cabal-1.4 Comment: This is just a matter of adding an `ArchVar` constructor to `PathTemplateVariable` in the `Distribution.Simple.InstallDirs` module. Then the `Arch` should be passed to `substituteTemplates` along with the `CompilerId` etc. This will make it possible for users to use `${arch}` in the install dirs like `--libdir` (or the equivalents in the cabal-install config file). Note that we're not proposing to actually change the default install paths, just to make it easy for users to do this themselves. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/312#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#312: Allow ${arch} var in install paths ----------------------------+----------------------------------------------- Reporter: larsv | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Cabal-1.4 Component: Cabal library | Version: 1.2.3.0 Severity: minor | Resolution: Keywords: | Difficulty: very easy (<1 hour) Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Comment (by igloo): Don't people with shared `$HOME`s already have ways to deal with this, e.g. passing `--prefix=~/i386` for configure/make programs, with `~/i386/bin` in their path? Wouldn't it make most sense for them to do the same for Cabal programs? And if they are doing something like that, then we won't know whether they want `$arch` to be `i386`, `i686`, `x86`, or something else. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/312#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#312: Allow ${arch} var in install paths
----------------------------+-----------------------------------------------
Reporter: larsv | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone: Cabal-1.4
Component: Cabal library | Version: 1.2.3.0
Severity: minor | Resolution: fixed
Keywords: | Difficulty: very easy (<1 hour)
Ghcversion: 6.8.2 | Platform:
----------------------------+-----------------------------------------------
Changes (by duncan):
* status: new => closed
* resolution: => fixed
Comment:
{{{
Tue Jul 29 16:19:52 BST 2008 Duncan Coutts
participants (1)
-
Hackage