FS#77839 - [pacman] prompt/notify the user when an existing file is overwritten
Attached to Project:
Pacman
Opened by Pratham patel (thefossguy) - Monday, 13 March 2023, 10:40 GMT
Last edited by Allan McRae (Allan) - Monday, 13 March 2023, 10:57 GMT
Opened by Pratham patel (thefossguy) - Monday, 13 March 2023, 10:40 GMT
Last edited by Allan McRae (Allan) - Monday, 13 March 2023, 10:57 GMT
|
Details
### Description
I recently received an update for the package `bspwm` and after the upgrade, I noticed that the behavior I noticed didn't align to how it configured it. After cursing Nvidia for breaking picom, I realized that the package provides `/usr/share/xsessions/bspwm.desktop` which overwrote my existing `bspwm.desktop` file. On Debian based distributions, when the existing file differs than the new file provided in the package, the user is prompted as following: ``` Configuration file '$ABSOLUTE_FILE_PATH' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** $FILE (Y/I/N/O/D/Z) [default=N] ? ``` Something similar should be done to Pacman, more so because Arch Linux is a rolling release and the user should at least be informed about such a change. |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 13 March 2023, 10:57 GMT
Reason for closing: None
Additional comments about closing:
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacm an/-/issues
Monday, 13 March 2023, 10:57 GMT
Reason for closing: None
Additional comments about closing:
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacm an/-/issues