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
..
check_pkg_files.c	xbps_api.h -> xbps.h	2013-06-20 12:31:02 +02:00
check_pkg_rundeps.c	Use C99 for loop initializers.	2013-09-15 10:06:49 +02:00
check_pkg_symlinks.c	Use C99 for loop initializers.	2013-09-15 10:06:49 +02:00
check_pkg_unneeded.c	Misc cleanups: use __attribute__((__unused__)); remove dead code.	2013-08-29 10:45:30 +02:00
check.c	Use a POSIX lock for pkgdb and only issue pkgdb writes in exact points.	2014-03-04 14:37:10 +01:00
convert.c	Use C99 for loop initializers.	2013-09-15 10:06:49 +02:00
defs.h	xbps_api.h -> xbps.h	2013-06-20 12:31:02 +02:00
main.c	Use a POSIX lock for pkgdb and only issue pkgdb writes in exact points.	2014-03-04 14:37:10 +01:00
Makefile	mk/prog.mk: set MAN to $(BIN).8 by default.	2013-09-16 08:57:24 +02:00
xbps-pkgdb.8	xbps-xxx.8: update issues url.	2013-12-17 15:38:56 +01:00