Re: Feature Idea: --no-remote-fetching flag

Hi Adam, On Tue, Oct 8, 2013 at 6:46 PM, Adam Foltzer wrote:

I'd be willing to explore implementing this myself, if it would be appropriate for a first-time cabal hacker. I'm also quite interested to hear whether this would be a useful feature for others, or other ways you might propose to address the problem.

I have an old patch lying around that implements offline mode for 'cabal install'. You may be interested in taking a look: https://github.com/23Skidoo/cabal/commits/offline-mode -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

From acfoltzer at gmail.com Tue Oct 8 16:46:57 2013 From: acfoltzer at gmail.com (Adam Foltzer) Date: Tue, 8 Oct 2013 09:46:57 -0700 Subject: Feature Idea: --no-remote-fetching flag Message-ID: X-List-Received-Date: Sat, 12 Oct 2013 07:40:56 -0000 X-List-Received-Date: Sat, 12 Oct 2013 07:40:56 -0000

Hello, With the wonderful advent of sandboxes in mainline cabal, I'd like to see what folks think of a flag to disable remote fetching of dependencies. The idea is that one could `cabal sandbox add-source` a set of trusted dependencies, and then be assured that a subsequent `cabal install --no-remote-fetching` would *only* resolve dependencies in that trusted set. I'd be willing to explore implementing this myself, if it would be appropriate for a first-time cabal hacker. I'm also quite interested to hear whether this would be a useful feature for others, or other ways you might propose to address the problem. I also understand that I can get this behavior by modifying the ~/.cabal/config, but this is a kludgey approach that is not workable in all deployment environments. Thanks! Adam