Fix a memleak involving lazy DB loading
commita2cd48960e33043f75c81e0ecbc2d33b20b695fe
authorXavier Chantry <shiningxc@gmail.com>
Mon, 7 Sep 2009 22:45:56 +0000 (8 00:45 +0200)
committerDan McGee <dan@archlinux.org>
Wed, 9 Sep 2009 02:43:06 +0000 (8 21:43 -0500)
tree9a70e1d291fa5978536e80e5181e4bd0bbaf3fbb
parent2e7c569950f3a6f651fb4850cb320068e2261198
Fix a memleak involving lazy DB loading

Lazy opening of databases is supported since 34e1413d75.

We don't need that setlibpath call each time we register a database.
Besides this caused a memleak in case setlibpath failed, because setlibpath
exit directly and we did not do the cleanup part (section string was not
freed, and a file descriptor remained open).

Signed-off-by: Xavier Chantry <shiningxc@gmail.com>
Signed-off-by: Dan McGee <dan@archlinux.org>
src/pacman/pacman.c