pmatilai left a comment (rpm-software-management/rpm#3750)
I don't want to ignore concerns over automatic migrations, I have my own
reservations too.
My thinking here is that since we place a symlink on the original file's
location, we can avoid an annoying nagging for almost every rpm(build) user out
there without affecting their lives significantly. Without the symlink, I
wouldn't dream of such a change. I edit my ~/.rpmmacros so often, I find the
new XDG-path nothing but annoying - for that purpose. It has its own benefits
of course. I have been wondering if it makes sense to perform the migration on
any type of rpm usage or should it be limited to some types of usages only -
but then what would those be?
Couple of initial remarks on the patch itself:
- the log messages should talk about migration rather than moving
- we should clean up what we did in case of a failed migration, because
otherwise a failing migration can cause a situation where both the old and new
file exist as normal files, but only the latter is honored, and THAT is
confusing/buggy behavior for the user
- ...which makes me think maybe there should be a flag file to track the
migration so we wont be trying the same thing over and over again
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3750#issuecomment-2882719018
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/3750/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
