CODEWITHSUNDEEP
haskelldependenciesdependency-managementcabal
artella
artella

Reputation: 5118

Using cabal-dev to avoid dependency conflicts

Currently I have cabal installed globally as specified in Installing cabal globally by Volker Schatz. In the post Understanding cabal dependency messages I was getting dependency conflicts when trying to install GOA, and would therefore like to try to install GOA via cabal-dev (cabal-dev by Rogan Creswick) in order to isolate the installation (if I understand it correctly cabal will include a sandboxing feature in the future, see cabal sandbox by Johan Tibell, but since it is still under development I would like to give cabal-dev a try).

Question : So given that my ~/.cabal is a symbolic link to /usr/local/share/cabal (as is done in url 1), how would I go about using cabal-dev to install GOA? Ideally the installation would still be placed in /usr/local/share/cabal, but maybe in a specialised directory like /usr/local/share/cabal/cabal-dev

Upvotes: 0

Views: 757

Answers (1)

dsign
dsign

Reputation: 12700

As I understand it, the purpose of cabal-dev is to create an isolated environment just for compiling your project or a specific set of subprojects with compatible dependencies. The only thing you need to do is to run cabal-dev in the directory of your "cabalized" project, and it will locate the correct set of version for all your dependencies and compile and install them locally, in "cabal-dev" of your subdirectory. If you asked it to do that in a centralized location, like "/usr/local/...", then you would be defeating the whole purpose of cabal-dev. If you are still in doubt, please check virtualenv... cabal-dev works in a somewhat similar fashion.

Upvotes: 1

Related Questions