Skip to content

implement the Cabal ${pkgroot} spec extension

See the proposal for relative paths in installed package descriptions:

http://www.haskell.org/pipermail/libraries/2009-May/011772.html

Basically it amounts to replacing ghc's current $topdir and $httptopdir with variables that are interpreted relative to the package db file itself rather than relative to where ghc is installed (though for the global package db these coincide).

The open question is how tools discover the location of the package dbs. The proposed spec extension does not specify this, but perhaps it should specify an extension to (the hypothetical) hc-pkg system to discover the default set of package dbs and their paths.

Trac metadata
Trac field Value
Version 6.10.2
Type FeatureRequest
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Package system
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information