fix comment
It turns out readFile does realise the context, so it could make a difference. I would still argue that's not our responsibility and your git config should be pointing ot paths that are already valid.
This commit is contained in:
parent
61ddc300c1
commit
81c6af2553
1 changed files with 5 additions and 3 deletions
|
|
@ -242,9 +242,11 @@ rec {
|
|||
for
|
||||
(guard (toLower section == "core" && toLower key == "excludesfile"))
|
||||
(_:
|
||||
# SAFETY: Ultimately this path will get passed into
|
||||
# `builtins.readFile`, which ignores the context anyways. The
|
||||
# context is only relevant if it becomes part of a derivation.
|
||||
# Paths with context can't be appended to other paths, so we have to
|
||||
# remove the context here.
|
||||
# SAFETY: gitignore.nix is not responsible for making sure the
|
||||
# store paths pointed to in your global git config have been
|
||||
# realised.
|
||||
resolveFile (home /.) (builtins.unsafeDiscardStringContext value)
|
||||
)
|
||||
)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue