installation advice on --force-reinstalls about req HOT 7 CLOSED

Why do you want to cabal install req? Use new- or v2- commands.

from req.

You create a .cabal file that describes your package and its dependencies and then you do cabal new-build or cabal v2-build and it builds it solving the package version constraints just for this single package in isolation. If you install packages globally you'll quickly find yourself in dependency hell. It's something we did in ~2013 or so.

Or use stack. Or use nix.

from req.

It's something we did in ~2013 or so.

I'm learning, so maybe a good lesson in package management.

I'm setting up a remote linux instance, where I can use http-client and req with ghci interpreter, so there really isn't a package I'm developping or supporting now.

I'm trying to get an example from req README to run. So far I installed haskell platfrom with sudo apt-get install haskell-platform and I want to run

Prelude> import Network.HTTP.Req

<no location info>: error:
    Could not find module ‘Network.HTTP.Req’

Is cabal install req --force-reinstalls too risky? Maybe I should reinstall HTTP after running it.

stack would be good for a package too, but not for global installation right?

nix I know nothing about yet, seems quite learning curve.

from req.

cabal install req --force-reinstalls worked fine for running a README example

from req.

Usually I experiment by creating a small project. You can do it either with stack or with cabal. I'm not sure why you need a remote linux instance though, you could do it locally on your computer.

The install commands are usually for binaries. What they do is they build the packages and put their executables on PATH (if configured properly).

from req.

Usually I experiment by creating a small project.

That's a useful tip, not usually found on tutorials. Should learn to use more often.

why you need a remote linux instance though

I'm locked on Windows - in my path I have non-latin characters for home directory, so many installations fail (eg entropy package) and WSL is not yet compatible with cabal and tools using it.

So my choices were either a big local virtualisation or a small remote machine. I use VS Code remote features to handle the remote, so in stable situation it is a good combo.

from req.

Should we close this one?

from req.