summaryrefslogtreecommitdiffstats
path: root/contrib/vimprojects
diff options
context:
space:
mode:
authorJonathan Frazier <eyeswide@gmail.com>2013-07-18 17:12:32 -0400
committerAllan McRae <allan@archlinux.org>2013-07-30 13:00:10 +1000
commita79661225a5d017864aefbacda50322ae1952df5 (patch)
treeba1cb1862bb1df12adbbf66cd2955c249bb5496a /contrib/vimprojects
parent15eea825e65e4ed1e7e186cb1f3535ed04b71373 (diff)
downloadpacman-a79661225a5d017864aefbacda50322ae1952df5.tar.xz
pacdiff: improve speed, accuracy finding active configs using pacmandb
This is a new search type, using -p or --pacmandb options. It reads config file locations directly from the local pacman db. It will find active configs anywhere they are defined in installed packages. It is not dependant on outside configs such as updatedb.conf or scanning a large set of directories for find. This will find more pacnews than find when searching with the current default of /etc, and it is faster than both find and updatedb when searching the entire fs. When run directly after an update, the local db is more likely to be cached than all files in /etc or / as other methods read. This will increase performance further post upgrade. After a package is removed and a pacsave is created, this method will not find these pacsaves until the base config is added to the local db again. These files have no influence in a working system and only take up a few blocks of disk space. Active configs need to be dealt with immediately to keep a system working. pacsaves related to removed configs can remain for weeks or months without problems. I would recommend occasionally running other methods such as --locate to remove them. Signed-off-by: Jonathan Frazier <eyeswide@gmail.com> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'contrib/vimprojects')
0 files changed, 0 insertions, 0 deletions