Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

default.css will not update to newer contents automatically #254

Open
trigg opened this issue Apr 28, 2024 · 0 comments
Open

default.css will not update to newer contents automatically #254

trigg opened this issue Apr 28, 2024 · 0 comments

Comments

@trigg
Copy link
Contributor

trigg commented Apr 28, 2024

I'm torn as to what I think is the correct path here.

Currently

  • default.css is populated on first run
  • if edited by user, it is not overwritten
  • if deleted by user, it is not replaced
  • if edited upstream, new edits in master/stable do not propagate to user

Worse idea

  • each update default.css is replaced with a new copy
  • if edited by user, it magically reverts
  • if deleted by user, it magically reappears
  • if edited upstream, new content is automatically applied

Midway solution

  • instead of a copy, use a symlink to the root-owned file
  • user will not be able to edit the contents
  • if deleted by user, it is not replaced
  • if edited upstream, new content is automatically applied

My personal opinion is to switch over to the midway solution as it still allows user to have ultimate say with the lowest likelihood of breakage from updates.

Naturally this is a call for opinions on the matter.

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

No branches or pull requests

1 participant