Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21342 - [vte] Please do not overwrite xterm config with every update.

Attached to Project: Arch Linux
Opened by Martin Dratva (raqua) - Tuesday, 19 October 2010, 17:15 GMT
Last edited by Jan de Groot (JGC) - Thursday, 21 October 2010, 13:14 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Every time vte is upgraded, file /usr/share/vte/termcap/xterm gets overwritten. I have terminal size set to be much bigger than default in Gnome and I have to edit this file every time it happens. Since this is generally just a config file, could it be treated as other config files are - if there are no changes, do not overwrite it and if there are, do pacnew file instead?
It is annoying the way it is now.
Thank you.
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 21 October 2010, 13:14 GMT
Reason for closing:  Won't implement
Additional comments about closing:  This is technically not a configuration file.
Comment by Karol Błażewicz (karol) - Tuesday, 19 October 2010, 17:35 GMT
I just want to add that /usr/share/vte/termcap/xterm is provided by vte from extra, so somebody might want to add [vte] to the bug report title.
Comment by Jan de Groot (JGC) - Thursday, 21 October 2010, 12:39 GMT
Files in /usr/share are technically not configuration files, and I haven't seen other distributions (Debian, Fedora) handling this file as a configuration file. If you want to preserve the file, you should add it to NoUpgrade in /etc/pacman.conf.
Comment by Martin Dratva (raqua) - Thursday, 21 October 2010, 12:45 GMT
I understand your point. But why is this file not in etc then - it seems like config file to me.
Anyway, if this NoUpgrade option will work (did not know about that option, thought it works only for packages), it is fine for me although there is risk the if there is some change in the file format or something similar I will never find out. :/
Comment by Jan de Groot (JGC) - Thursday, 21 October 2010, 13:13 GMT
Adding it to NoUpgrade will do the same as placing it in backup= in the package: you'll get a .pacnew file. After looking into git, I don't even think this file will get changed at all in the future, as the last modification was 8 years ago.

Loading...