Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update from version 2 to 3 loses config #1032

Open
3 tasks done
ldesousa opened this issue Jul 17, 2024 · 1 comment
Open
3 tasks done

Update from version 2 to 3 loses config #1032

ldesousa opened this issue Jul 17, 2024 · 1 comment
Labels
bug Something isn't working needs-triage Any bug that requires classification by a contributor

Comments

@ldesousa
Copy link

Describe the bug
The update from version 2 to 3 leaves the user config in the ~/.config/regolith2 folder, which is ignored afterwards.

To Reproduce
Update from version 2 to 3.

Expected behavior
The configuration should be kept between versions, without user intervention.

Screenshots
Not applicable.

Configuration file(s)
Full details in discussion 1031.

Installation Details

  • Regolith Install Type: PPA
  • Regolith Version: 2 and 3
  • PPA url: ppa:regolith-linux/release
  • Host OS (for PPA): Ubuntu 22.04
@ldesousa ldesousa added bug Something isn't working needs-triage Any bug that requires classification by a contributor labels Jul 17, 2024
@kgilmer
Copy link
Member

kgilmer commented Aug 18, 2024

Hi @ldesousa ,

The configuration should be kept between versions, without user intervention.

I guess we have a difference of opinion regarding policy. In previous major (aka "breaking") releases I found that often people would get upgrades without realizing it and it would cause them unexpected problems. I am guessing this is in part due to the relatively high "expressibilty" of the i3/sway configuration files. As such, I decided that upon major versions, the configuration root would change, requiring users to explicitly move over their configuration files over.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Any bug that requires classification by a contributor
Projects
None yet
Development

No branches or pull requests

2 participants