How is the update process of an existing install

[JuanPardos]

First of all congrats for this awesome rice :)

I want to know how is the process of updating an existing install.
I am not new in the Linux rice environment as I have used other hyprland configs like hyprdots and similar, in most of them the update was a pain in the a...
I had to specify every config I didn't want to be overwritten by the script and so on...

I mean I don't want an obsolete install every 2 weeks and neither taking 1 hour tweaking things before even updating (I know hyprland rices are "experimental").

Will my personal config get overwritten every update ? Will I get new features/components/widgets seamlessly ?
Don't have time or knowledge to scout all the repo but I might install this very soon once I get bored of my KDE plasma.
I have checked main readme and also cli repo but I can't find any references to updating.

Thanks in advance, keep up with the excellent work.

[anispwyn]

If you overwrite everything it just come out working as normal

[soramanew]

First of all congrats for this awesome rice :)

I want to know how is the process of updating an existing install.
I am not new in the Linux rice environment as I have used other hyprland configs like hyprdots and similar, in most of them the update was a pain in the a...
I had to specify every config I didn't want to be overwritten by the script and so on...

I mean I don't want an obsolete install every 2 weeks and neither taking 1 hour tweaking things before even updating (I know hyprland rices are "experimental").

Will my personal config get overwritten every update ? Will I get new features/components/widgets seamlessly ?
Don't have time or knowledge to scout all the repo but I might install this very soon once I get bored of my KDE plasma.
I have checked main readme and also cli repo but I can't find any references to updating.

Thanks in advance, keep up with the excellent work.

The updating for the shell and cli are done through aur packages, so you shouldn't be editing those anyway. For shell configs, there is a config file in ~/.config/caelestia but if you want to make your own changes to the code I recommend cloning the shell repo into ~/.config/quickshell/caelestia and using git pull/merge to update it.

[Vasabii]

@soramanew When running yay -S caelestia-shell-git it doesn't update anything because the files already exist. Is there a way to overwrite them?

[soramanew]

@soramanew When running yay -S caelestia-shell-git it doesn't update anything because the files already exist. Is there a way to overwrite them?

Hmm, updating works perfectly fine for me. Did you edit any of the files in /etc/xdg/quickshell/caelestia by any chance?

[Vasabii]

Hmm, updating works perfectly fine for me. Did you edit any of the files in /etc/xdg/quickshell/caelestia by any chance?

Ah, I didn't quite understand how the git pull command works. I did, and you're not supposed to make any manual changes to it at all, only then git pull works. The man page is very confusing.

If anyone's reading that also changed the code -- running

cd /directory with a .git dir in it/
git reset --hard

Overwrites all the files in the directory with the main branch's files

[soramanew]

Hmm, updating works perfectly fine for me. Did you edit any of the files in /etc/xdg/quickshell/caelestia by any chance?

Ah, I didn't quite understand how the git pull command works. I did, and you're not supposed to make any manual changes to it at all, only then git pull works. The man page is very confusing.

If anyone's reading that also changed the code -- running

cd /directory with a .git dir in it/
git reset --hard

Overwrites all the files in the directory with the main branch's files

Please don't edit the files in /etc/xdg/quickshell/caelestia (manually editing package files isn't a good idea). If you want to make your own config, clone it into ~/.config/quickshell/caelestia like I said above