You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature request
I'm looking for global option or command line option that allows cabal to continue to function when dependencies are provided by nix and there is no package list from hackage.haskell.org. Unfortunatly, the offline option does not skip the required cabal update step. A reasonable solution would be to modify the offline flag to skip checking for a valid package list. (I have only tested with 3.12.1.0)
Additional context
The underlyning issue is that the new versions of cabal commands break the nix workflow, where nix provides all the dependecies and cabal only tries to build the project with the provided dependencies, no network requests. With version 3.12.1.0, cabal will silently pull in missing dependencies even when the offline flag is set. However, there is a workaround, setting active-repositories: :none option does prevent this. Sadly, no combination of options (including nix: True) removes the package set requirement.
The text was updated successfully, but these errors were encountered:
Describe the feature request
I'm looking for global option or command line option that allows cabal to continue to function when dependencies are provided by nix and there is no package list from hackage.haskell.org. Unfortunatly, the
offline
option does not skip the requiredcabal update
step. A reasonable solution would be to modify the offline flag to skip checking for a valid package list. (I have only tested with3.12.1.0
)Additional context
The underlyning issue is that the new versions of cabal commands break the nix workflow, where nix provides all the dependecies and cabal only tries to build the project with the provided dependencies, no network requests. With version
3.12.1.0
, cabal will silently pull in missing dependencies even when theoffline
flag is set. However, there is a workaround, settingactive-repositories: :none
option does prevent this. Sadly, no combination of options (includingnix: True
) removes the package set requirement.The text was updated successfully, but these errors were encountered: