You are not logged in.
I just noticed - while trying to make a CD-sized iso - that bunsen-themes is a big package at ~70MB. Surprising, since themes are mostly text files and tiny images. Looking inside, I found each theme has a gtk-3.0/.sass-cache directory which seems to be taking up most of the space.
A cache doesn't sound essential, and a bit of Googling suggested this data speeds up the recompiling of gtk3 themes after config changes. General users won't be doing that so often I guess. How about deleting all those .sass-cache directories? It would reduce the package size dramatically. Any hidden gotchas?
Last edited by johnraff (2018-05-17 02:27:01)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Nope, killing the cache is fine for pre-compiled themes. E.g. for arc-theme when you user make install it just ignores the .sass-cache.
Offline
Base users 1) generally don't recompile the theme; 2) cannot recompile without adding package ruby-sass; and 3) get the cache recreated from the sources if not present.
Just kruft for the vast majority. Delete? Please and thank you.
Offline
Base users 1) generally don't recompile the theme; 2) cannot recompile without adding package ruby-sass; and 3) get the cache recreated from the sources if not present.
Just kruft for the vast majority. Delete? Please and thank you.
Correct (*can get the cache...) and agreed, just keep the sass files on GitHub. Delete is seconded, please and thank you.
I don't care what you do at home. Would you care to explain?
Offline
OK deleted in bunsen-themes 9.4.1-1, coming to a computer near you, shortly.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline