- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Drop automatic migration of configuration from ~/.mc to XDG-base #3682
Comments
Just to clarify:
There are two migration mechanisms:
You're talking about removing only (1), right? Because we're still going to need (2), to fix issues like #3687 (in the future we might want to relocate other files similarly).
In (2) it's probably fine to remove the current rules, though. These rules were added in Nov 2011 (commit 25c9267), less than a year after XDG support was added (Dec 2010, commit acbe048). |
Some food for thought:
It's possible to compile MC without XDG support. Maybe we should keep the migration code so it could be used (in the future) to migrate these users to XDG?
Feel free to discard this quick note: I haven't thought much about it. |
I'd say that dropping it now is very premature: RHEL 6 is shipping mc-4.7.0.2 by default (EOL: 2020) and RHEL 5 (EOL: 2017 / 2020) is shipping mc-4.6.1a. I'm not sure what's the situation with SLES, but I bet the situation is similar. I'm not necessarily saying that we have to wait at least 4 more years, but maybe at very least until RHEL 8 comes out. There are still tons and tons of homes to be upgraded... |
I think it's time to do that. It's 2021 now. |
Fine by me. |
Branch: 3682_drop_automatic_config_migration |
|
|
Important
This issue was migrated from Trac:
andrew_b
(@aborodin)zaytsev
(@zyv)Before 4.8.1, the mc configuration was locate in ~/.mc directory. After implementation of XGD-based configuration (#1851), mc copies configuration from old directory to new XDG-based place if it doesn't exist and then uses it.
Now after 4 years we can drop this automatic migration and clean up the codebase.
The text was updated successfully, but these errors were encountered: