How to keep the selected non-default folder style over Numix base PPA updates about numix-folders

[Foggalong]

Not without doing something like Ozon where each style is a separate theme. That has potential to cause problems with inheritance with Numix and would mean loads and loads of themes if colours are taken into account.

@paolorotolo Is there anyway packaging wise to stop it overwriting files that aren't changed in the git (but might be different on the local machine)?

[dirtydancing]

Alternatively, might there be a way to trigger the script automatically when an update is detected? This automatic triggering of the script should only happen if a non-default folder style has been selected via the script before (i.e. not for the default style, as that will be displayed per default anyways). Just an idea.

[Foggalong]

That's possible, but it would add a lot of baggage to the script such as an installer and a need for it's own data directory.

[Foggalong]

Gonna say no to this. While it'd be an awesome feature to have, the overhead would be too significant to implement :( Maybe one day, possibly when Snappy is default, if PPAs ever become more flexible to operate

[bilelmoussaoui]

@Foggalong I guess you can create a folder in .config or a hidden file where you put the default values as default style, default color. Whenever the ppa updates, you check if the file exists if so, gets get back folder to it's default values. If not, keep the default one. This might not be that hard to do

[Foggalong]

That's not really the hard bit - it would involve setting up a system to watch for PPA updates which is out of the scope of this project :(

[dirtydancing]

Cf. the further discussion over at #101.