serpent-os / tools

The home of moss (system state manager) and boulder (moss format build tool)
https://serpentos.com
137 stars 12 forks source link

moss: Work on `moss state info` UX #312

Open ermo opened 3 months ago

ermo commented 3 months ago

Given the moss state mechanism appears to be working as expected, it might be wise to begin looking at how to make the feature more discoverable and more user friendly.

Iterms to consider:

Ikey Doherty Yeah for moss state we basically should by default compare it with the state before it And make it more like eopkg history And using the same comparison function allow checking diff between two unrelated states Ie 1 vs 550 In time I'd like to unlock full introspection so that the full system use is visible, opportunities to shrink moss size, etc Ie cache size, old states Just so it's obvious at a glance "Oh I can free up xyz gb" Tldr nobody needs to be a shell guru to inspect moss Ravi Jain If you had 500 transactions and could go back to the very first one. I know you have prune function but over time, wouldn't that balloon your install size? What's the default behaviour for auto-prune or isn't there one? Ikey Doherty We don't autoprune yet