I use direnv and one of the things it does is create an immutable .direnv/ directory (or possibly it just creates links to the Nix store, which is immutable, I don't remember exactly) over which the current user does not have permissions. When newsitewalks the file tree and tries to change the files' mode it fails on the first .direnv/ file it reaches
meaning that any files that are due to have their mode changed after that will be missed.
I think the "correct" fix here would be to only try to change the modes of files that are under Franklin's purview, but doing that properly in a way that is resilient to future changes is probably far more effort than it's worth. Instead I think a more pragmatic fix would be to either wrap the chmod call in a try or maybe allow the user to pass a list of paths to ignore when running it.
I also understand if you don't think this is a common enough problem to be worth maintaining a fix, since this is definitely a very niche issue.
I use direnv and one of the things it does is create an immutable
.direnv/
directory (or possibly it just creates links to the Nix store, which is immutable, I don't remember exactly) over which the current user does not have permissions. Whennewsite
walks the file tree and tries to change the files' mode it fails on the first.direnv/
file it reachesmeaning that any files that are due to have their mode changed after that will be missed.
I think the "correct" fix here would be to only try to change the modes of files that are under Franklin's purview, but doing that properly in a way that is resilient to future changes is probably far more effort than it's worth. Instead I think a more pragmatic fix would be to either wrap the
chmod
call in atry
or maybe allow the user to pass a list of paths to ignore when running it.I also understand if you don't think this is a common enough problem to be worth maintaining a fix, since this is definitely a very niche issue.