Juan RP 0416b067d0 Use a POSIX lock for pkgdb and only issue pkgdb writes in exact points. ... - Rather than using a POSIX named semaphore use a POSIX lock (lockf(3)) for pkgdb for writers. Writers that cannot acquire the pkgdb lock will get EAGAIN rather then being blocked. - Due to using a file lock we cannot write the pkgdb every time a package is being unpacked, configured or removed. Instead pkgdb is only written at the end of a specific point in the transaction (unpack, configure, remove) or via xbps_pkgdb_unlock().		2014-03-04 14:37:10 +01:00
..
xbps
compat.h	Remove the config.h kludge and override vasprintf detection via HAVE_VASPRINTF.	2014-01-20 18:50:33 +01:00
mainpage.h
Makefile
queue.h
xbps_api_impl.h	include/xbps_api_impl.h: confuse.h is not necessary anymore.	2014-02-25 17:04:13 +01:00
xbps.h.in	Use a POSIX lock for pkgdb and only issue pkgdb writes in exact points.	2014-03-04 14:37:10 +01:00