Closed JustusAdam closed 5 years ago
etlas-1.3.0.0
uses cabal's new-build system which maintains a Nix-like package store and removes the need for sandboxes or the concept of installing packages to a global package database. etlas build
automatically installs dependencies into this store now, while etlas install
continues to follow the old system. We will eventually deprecate this behavior and currently waiting to see how Cabal devs implement new-install
.
You shouldn't have a reason to use etlas install
with etlas-1.3.0.0
and above since etlas build
+ (optional cabal.project
) file is all you need for most setups.
Above, running etlas install --dependencies-only
permanently installs to the global package store which will mess up your local setup and quickly get you into dependency hell.
Ah, very nice. I had no idea. In the old versions it was still complaining that i have to install deps first.
I'll try that
@JustusAdam Last released etlas (1.5.0.0
) already uses by default the nix-like package store so it is in sync with etlas build
(no need for --dependencies-only
) so i think we can close this.
This might actually be an issue with cabal itself, but for some reason executing
etlas install
(with and without--dependencies-only
) works fine, whereasetlas build
reports dependency resolution errors.Reproduce
To clarify what I did
etlas sandbox
add-source
dependencyetlas install --dependencies-only
(that worked just fine)However when I now try
etlas build
I get this:If, instead, I run
etlas install
it actually compiles the project just fine. This indicates to me that there's some discrepancy between thebuild
andinstall
command. I always thought thatinstall
was likeconfigure
+build
+ copy binaries, but it seems that is not the case.Additional information
rm -rf ~/.eta ~/.etlas
)eta
andeta-*
binaries andetlas
etlas
and ranetlas update
dist
folders and sandboxes.1.3.0.0
0.7.2b1
(revfb8e6f4604e4b94d8d2dc01380256f9c8c28bced
)