dmnks left a comment (rpm-software-management/rpm#3750)
I'm a bit late to the party but here's my thoughts:
This seems like a bad idea to me. The amount of code this requires, plus the
risk of missing one of those corner cases (did we really consider them *all*?),
are all red flags for me. I'm of the opinion that one's `$HOME` directory
shouldn't be messed with like this. More so if it's something that the user
isn't aware of *before* it's done on their behalf.
There's also one scenario which I don't see mentioned here, which is
[managing](https://news.ycombinator.com/item?id=32253018) one's dotfiles with
something like [GNU Stow](https://www.gnu.org/software/stow/manual/stow.html)
(which I personally do). In such a case, I'd already have a symlink at
`~/.rpmmacros` which points to my dotfiles.git repository somewhere else, which
the automatic migration would break.
Yes, it would be nice if we could rely on there being a `~/.config/rpm`
directory, but I don't see that as worth the risk, especially since we
currently [don't have an actual
need](https://github.com/rpm-software-management/rpm/pull/3750#issuecomment-2890022227)
for it.
[Currently](https://github.com/rpm-software-management/rpm/commit/f24ca5eade57ebfafd3829aa6d4bfe5ab6f965be),
we fall back to the legacy locations completely if just one of those files
exists. Couldn't we make this fallback per-file instead? That way, no migration
would be required and we could still benefit from having `~/.config/rpm` to
ourselves for what we need.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3750#issuecomment-3058075198
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
