Hello, I think upgrade experience is suboptimal and we can definitely make it easier / smoother in some ways. I just wanted to throw some ideas in, feedback welcome 🙂
v0.3.8 -> v0.3.12
Just update the version in your config file.
This kind of upgrade sounds like it shouldn't require human intervention at all. Can we make xplr
itself bump the version? Or make config version independent on xplr
version, such that config version is 1
, 2
, 3
, ..., bumped only when needed, and xplr
knows for example that v0.3.8
requires config version of 12
?
xplr | yq ".config" -y | tee ~/.config/xplr/config.yml
I must say this is very cool idea, but maybe we can also provide a default config to make it a bit easier - you can do it in the repo (e.g. kak-lsp project keeps kak-lsp.toml
in the repo and uses it like so) or if you don't think it's a good idea, we can also just generate the config file directly in the AUR pkg, and place it e.g. in /usr/share/xplr/examples/config.yml
(cc @orhun).
v0.3.7 -> v0.3.8
...
Else, do the following:
Can we have this changelog not only in wiki, but also in the code / package somehow? Just imagining, I updated xplr
, then disconnected from internet, and then I run xplr
and uh-oh I must upgrade config but I dont know how without looking at the wiki!
Maybe a simple changelog file that we could also package?
And finally, maybe we can simplify config upgrade for Arch users even more if we leverage pacdiff? In that case honestly I might not even need to look in changelog, if only the lines changed that I didnt edit myself.
This would mean we would need to support reading config not only from ~/.config/xplr/config.yml
but also from /etc/xplr/config.yml
(which is used only if there is no config in the user dir), and then in PKGBUILD we place the config here instead of in examples
folder and mark it with backup=
field (cc @orhun). It would require keeping config in /etc
dir, so not sure if you like this, but I'm just brainstorming 🙂