
Cabal sandboxes as it stands right now are not portable at all, global
paths are only the beginning. For example you cannot use a sandbox created
on another machine by default, unless you have *exactly* the same
environment (e.g. use the same build of the Haskell Platform).
I wrote a small tool called SandFix that we use internally at my workplace
that fixes global paths and tries to fix all package dependencies as well
so you can reuse a sandbox created on another machine. I uploaded it now to
github: https://github.com/exFalso/sandfix. It works quite well for us.
Note that it assumes a ghc environment.
On 10 October 2014 21:00, Markus Läll
I would also prefer relative paths for sandboxes.
On Fri, Oct 10, 2014 at 4:34 PM, Corentin Dupont < corentin.dupont@gmail.com> wrote:
This project seems to do what you want (I didn't test it): https://github.com/philopon/sandbox-move
Although I think it would be better to have relative file paths in cabal.sandbox.config...
On Fri, Oct 10, 2014 at 4:29 PM, Brandon Allbery
wrote: On Fri, Oct 10, 2014 at 10:14 AM, Vlatko Basic
wrote: There is no way to move the project to a different place without recreating the whole sandbox.
It would be nice if there were a tool to do this. It should not be difficult to programmatically adjust those paths and the ones in the ghc package directory, and reindex the latter.
-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
-- Markus Läll
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe