Skip to content

Elevate permissions on directory access and filepath comparison#215

Open
archnode wants to merge 4 commits into
SuperCuber:masterfrom
archnode:103-elevate-permissions
Open

Elevate permissions on directory access and filepath comparison#215
archnode wants to merge 4 commits into
SuperCuber:masterfrom
archnode:103-elevate-permissions

Conversation

@archnode
Copy link
Copy Markdown

@archnode archnode commented May 7, 2026

Closes #103

There are a few instances where we have to be more liberal with elevating permissions to get consistency when using different owners.

@archnode
Copy link
Copy Markdown
Author

archnode commented May 7, 2026

This leads to further headache when having to delete changed symlinks. I added further changes to the target cache handling.

I'm not sure if my usecase that necessitates this makes sense for dotter in general:

  • User A (with sudo) checks out config repo in /usr/local/share
  • User A uses dotter to deploy config to system, user A homedir and user B homedir.

Probably a viable workaround would be:

  • Use sudo with dotter in combination with hardcoded paths and owners OR
  • Run dotter for each user seperately with different local.toml files

I still think the changes make the system with privilege elevation more consistent, but I'm unsure if that is something dotter should concern itself in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Dotter doesn't elevate if it can't read a directory

1 participant