Changes between Version 2 and Version 3 of SandboxedBuildsAndIsolatedEnvironments

Timestamp:

06/07/12 14:23:30 (12 months ago)

Author:

refold

Comment:

small fixes

SandboxedBuildsAndIsolatedEnvironments

@@ -51 +51 @@
 == Revise the UI and polish ==
 
-Implementing `build`, `test`, `bench` and others as `cabal sandbox` subcommands is redundant. These commands should be made aware of whether there is an sandbox active; they should be also changed to run `configure` and install dependencies automatically.
+Implementing `build`, `test`, `bench` and others as `cabal sandbox` subcommands is redundant. The top-level versions of these commands should be made aware of whether there is an sandbox active; they should be also changed to run `configure` and install dependencies automatically.
 
 Example session:
@@ -64 +64 @@
 }}}
 
-We can also remove the `cabal sandbox` subcommand completely and make `cabal build` initialise a sandbox implicitly when there is none; this will give us [http://blog.johantibell.com/2012/03/cabal-of-my-dreams.html hermetic builds]. [http://www.google-melange.com/gsoc/project/google/gsoc2012/phischu/19001 Philipp Schuster's project], if successful, will make this option more practical. 
+We can also remove the `cabal sandbox` command completely and make `cabal build` initialise a sandbox implicitly when there is none; this will give us [http://blog.johantibell.com/2012/03/cabal-of-my-dreams.html hermetic builds]. [http://www.google-melange.com/gsoc/project/google/gsoc2012/phischu/19001 Philipp Schuster's project], if successful, will make this option more practical. 
 
 = Progress =