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
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.
The text was updated successfully, but these errors were encountered:
I'm torn as to what I think is the correct path here.
Currently
Worse idea
Midway solution
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.
The text was updated successfully, but these errors were encountered: