what packages and conf files to avoid updating

vajorie · 2009-03-13 13:23:57

I was just wondering what packages, groups, and configuration files people put in the pacman.conf so that they are not updated... just to get an idea. thanks.

brisbin33 · 2009-03-13 13:54:32

i'm a bit confused on this myself. as far as i can tell, pacman will never just up and overwrite a config file, it'll instead leave a .pacnew version that you have to merge in manually. because of this, i think the NoUpgrade line is kinda pointless in pacman.conf. am i wrong? nevertheless, i still put sshd_conf and vsftpd.conf in there just b/c those would pose pretty big security risks if overwritten with default options.

as for IgnorePkg, i only use that for packages i've patched or purposely kept downgraded, so that would be up to you.

mcmillan · 2009-03-13 15:15:03

Generally people keep everything updated, unless there's some specific problem with a package so I want to keep an older one.

as far as i can tell, pacman will never just up and overwrite a config file, it'll instead leave a .pacnew version that you have to merge in manually. because of this, i think the NoUpgrade line is kinda pointless in pacman.conf. am i wrong?

This is mostly right. Whether a file is overwritten or saved as a .pacnew file is specified in the PKGBUILD. For the most part this has dealt with any changes in config files well enough. The exception is when you start tweaking things that aren't generally modified. For example I discovered this after making some modifications to my /etc/rc.sysinit file. Unfortunately this got overwritten with the next update to initscripts. So NoUpgrade could be useful if you want to save files like this that aren't included in the backup array. (though out of curiousity I just looked and it seems rc.sysinit is now included to get a .pacnew)

Mr.Elendig · 2009-03-13 16:53:18

vajorie wrote:

I was just wondering what packages, groups, and configuration files people put in the pacman.conf so that they are not updated... just to get an idea. thanks.

Ignoring updates often leads to more problems than it solves...

Dheart · 2009-03-13 17:51:34

Only wine - when a new wine is out I manually build it, cause I patch few things (accept_ex for Frozen Throne hosting and event.c for minimizing in opengl mode).

test1000 · 2009-03-13 19:39:48

@Dheart, winehacks?

Last edited by test1000 (2009-03-13 19:40:37)

Dheart · 2009-03-13 20:13:17

winehacks contains too many hacks and patches, that I don't need - I just manually patch with patches for the software I'm using.

skottish · 2009-03-13 20:38:40

IgnorePkg = gpac gtkpod gnome-mplayer easytag gecko-mediaplayer gamin linphone

gpac, gtkpod, easytag, and linphone are all because I don't have anything from Xiph (vorbis, theora, etc) other than speex installed, as well as I use my own builds of FFmpeg. I don't rename them because I want to know if there's an update to any of these packages.

gnome-mplayer and gecko-mediaplayer because they have things I don't need or want.

gamin because pcmanfm and gamin 0.1.0 don't play nice.

Arch Linux

#1 2009-03-13 13:23:57

what packages and conf files to avoid updating

#2 2009-03-13 13:54:32

Re: what packages and conf files to avoid updating

#3 2009-03-13 15:15:03

Re: what packages and conf files to avoid updating

#4 2009-03-13 16:53:18

Re: what packages and conf files to avoid updating

#5 2009-03-13 17:51:34

Re: what packages and conf files to avoid updating

#6 2009-03-13 19:39:48

Re: what packages and conf files to avoid updating

#7 2009-03-13 20:13:17

Re: what packages and conf files to avoid updating

#8 2009-03-13 20:38:40

Re: what packages and conf files to avoid updating

Board footer