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-create	xbps-create: do not use FTW_MOUNT with nftw(3).	2014-01-08 20:16:02 +01:00
xbps-dgraph
xbps-install	New custom configuration file format that does not need confuse.	2014-02-25 16:42:52 +01:00
xbps-pkgdb	Use a POSIX lock for pkgdb and only issue pkgdb writes in exact points.	2014-03-04 14:37:10 +01:00
xbps-query	Keep repo metadata if possible when updating repodata (xbps-rindex -a/-c).	2014-01-30 13:07:34 +01:00
xbps-reconfigure	Use a POSIX lock for pkgdb and only issue pkgdb writes in exact points.	2014-03-04 14:37:10 +01:00
xbps-remove	New custom configuration file format that does not need confuse.	2014-02-25 16:42:52 +01:00
xbps-rindex	Revert "xbps-rindex: [sign] free pubkey data obj after externalizing index-meta."	2014-02-06 16:34:59 +01:00
xbps-uhelper	xbps-uhelper fetch supports user defined output file	2014-03-04 14:22:02 +01:00
Makefile