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
Add 'allow-different-user' flag and configuration option #471, fix#1777
Users other than the owner of the ~/.stack directory are now prevented
from using a stack installation in order to avoid problems with file
permissions. To disable this precaution users can pass the
--allow-different-user flag or use the 'allow-different-user'
configuration option in their ~/.stack/config.yaml.
On Windows, the new flag and configuration options have no effect.
When stack is re-spawned in Docker, the ownership check is skipped
(see #1777).
This reverts commits 0a89c9c and
218e7dd.
Copy file name to clipboardExpand all lines: doc/yaml_configuration.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -435,6 +435,22 @@ allow-newer: true
435
435
Note that this also ignores lower bounds. The name "allow-newer" is chosen to
436
436
match the commonly used cabal option.
437
437
438
+
### allow-different-user
439
+
440
+
(Since 1.0.1)
441
+
442
+
Allow users other than the owner of the stack root directory (typically `~/.stack`)
443
+
to use the stack installation. The default is `false`. POSIX systems only.
444
+
445
+
```yaml
446
+
allow-different-user: true
447
+
```
448
+
449
+
The intention of this option is to prevent file permission problems, for example
450
+
as the result of a `stack` command executed under `sudo`.
451
+
452
+
The option is automatically enabled when `stack` is re-spawned in a Docker process.
453
+
438
454
### templates
439
455
440
456
Templates used with `stack new` have a number of parameters that affect the generated code. These can be set for all new projects you create. The result of them can be observed in the generated LICENSE and cabal files.
0 commit comments